Re: Gopher over TLS
Sean Conner <sean-/[email protected]> Mon, 6 Dec 2021 03:37:15 -0500
| Newsgroups | gmane.network.gopher.general |
|---|---|
| Message-ID | <[email protected]> |
It was thus said that the Great Mateusz Viste once stated: > On 06/12/2021 07:38, Sean Conner wrote: > > It's happening again. There's a gopher client (or proxy) that is > >attempting to request a page from my gopher site via TLS, *then* regular > >TCP. I still don't think TLS is a viable option for TLS [1] but hey, > >differing opinions and all that. I just think that if any client wants to > >use TLS over gopher, follow the above advice. Thank you. > > Gopher over TLS is a silly idea in the first place. What you describe > seems to be a gopher client/proxy attempting TLS over the standard > gopher port (70) - is that correct? Yes, that is correct. > If so, then we're beyond silly, that > is plain stupid territory. My opinion as well. > I hear about this gopher/TLS abomination since many years now. Haven't > those TLS-people figured out a non-intrusive way to do their thing by > now without bothering standard-gopher-people? ie. some DNS SRV record, > or special URL marking, or CAPS capability, or custom port, or something > else? It's not that easy---I wrote about this a few years ago [1] and relatively recently [2], which briefly goes into how I think people expect this to work. -spc [1] http://boston.conman.org/2019/03/31.1 [2] http://boston.conman.org/2021/09/28.1