Re: Gopher over TLS
Emil Engler <[email protected]>
| Newsgroups | gmane.network.gopher.general |
|---|---|
| Message-ID | <[email protected]> |
Glad to see you are still working on this (Sebastiaan)! Interested in writing an RFC and submit it to the RFC Editor? Cheers, Emil Am 12.05.20 um 05:41 schrieb Sean Conner: > It was thus said that the Great Sebastiaan Deckers once stated: >> FWIW, I drafted a spec of Gopher over TLS. Published the server and client >> libraries and deployed them in production. >> >> https://gitlab.com/commonshost/goth#gopher-over-tls-got-protocol > > Not bad, I like it. I also would *love* if the existing clients that > attempt TLS over gopher would follow this bit: > > > If the TCP/IP socket was successful but the attempt fails without > receiving a ServerHello message, a GoT client may attempt to connect > without TLS, treating the connection as plaintext Gopher. This > failure may be cached for as long as the server's DNS records are > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > valid. > ^^^^^ > > There's at least one client out there (I think it's a web-to-gopher proxy) > that attempts to ust TLS *every damn time* it makes a request and frankly, > I'm close to just outright blocking that IP address. Once a day (the > current TTL for 'gopher.conman.org') isn't bad, but *every single time* is > just rude (in my opinion). > > -spc (My other pet peeve of gopher clients is the notion that every > selector starts with a '/' ... ) >