Re: TLS in Gopher
On Wed, 28 Feb 2018 06:12:35 -0800 (PST)
Cameron Kaiser <spectre@floodgap.com> wrote:
>
> I'm not aware of any TLS wrapper that knows how to do this (it would
> require a lot of wire-level work to be even possible), and I'm sure
> many non-TLS servers would not respond favourably. With a categorical
> port, you know exactly what you're connecting to and what it's
> expecting.
>
Thought about this a bit; I do think that the STARTTLS suggestion would
be harder to write clients for, but I also don't like the idea of
defining specific ports for TLS and plaintext. TLS support can be
easily indicated in the URI by using "gophers://" in place of
"gopher://";. In menus, what about specifying this using the host field
instead of the port? For example,
"1example<TAB>/example<TAB>tls://example.com<TAB>70"
Alternatively, there could be a new item-type that is to be interpreted
like the existing '+' mirror type: instead of specifying a duplicate of
the last entry it would specify a TLS version, possibly with the same
host/port.
Reply to: