[gopher] Gophernicus 2.4 "Millennium Edition" released

[James Mills]

Can we just assume TLS if the destination port in the menu is 73 for
example?


James Mills / prologic

E: prologic at shortcircuit.net.au
W: prologic.shortcircuit.net.au

On Sun, Feb 5, 2017 at 2:16 AM, Kim Holviala <kim at holviala.com> wrote:

>
> > On 04 Feb 2017, at 12:11, Cameron Kaiser <spectre at floodgap.com> wrote:
> >
> >> The only remaining problem is to figure out a way to tell which
> connections
> >> are TLS and which are plaintext in gopher menus. Alternative is not to
> >> change menus at all and require the clients to read caps.txt first to
> see
> >> if there is a non-zero ServerTLSPort available for encrypted
> connections.
> >> That might actually be the most backwards-compatible method.
> >
> > That would certainly seem the most reasonable approach to me.
>
> I agree. I tried to come up with a way to add some kind of "encrypted or
> not" flag in the menus... but the existing servers and clients out there
> are *so* broken that I couldn't come up with a way that would not break
> things.
>
> Oh well. Some day I'll try to patch Lynx or something to work with gopher
> over TLS.
>
>
>
> - Kim
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20170205/7f136f47/attachment.html>