Re: TLS in Gopher

["Iain R. Learmonth" <irl@fsfe.org>]

Hi,

On 01/03/18 09:23, Nuno Silva wrote:
> But gopher with TLS is not gopher. The TLS handshake is not gopher. It
> *is* a distinct protocol with a different behaviour. IMHO not making it
> something clearly separated from gopher may cause more breakage.

If your server is going to crash when it sees something that is not a
well crafted Gopher selector, it shouldn't be on the Internet. Servers
should be resilient to all sorts of crazy inputs. It would be
interesting to see some fuzzing of Gopher servers/clients.

> You could also cache failures on the "gophers" port and retry with plain
> gopher on port 70.

Currently I have 65,535 options for my gopher port, but I'm only going
to have one for Gopher+TLS? That seems like a ridiculous restriction
that doesn't need to exist.

Thanks,
Iain.