Hi!There is a lot that TLS could make possible; in fact, we could get virtual hosting without having to bake it into the Gopher protocol thanks to SNI, and it makes sense to add this kind of protection to the modern Internet.
My only concern is that running TLS over port 70 will bifurcate Gopherspace. A given host will have to choose to either support the legacy clients or the new ones, and can't do both on the same IP & hostname. Would we still have time to pop it over to some other port, say 770 or 7070 or something, before this gets established?
- John On Mon, Dec 21 2020, Emil Engler wrote:
It's basically just a Gopher connection through a TLS layer. Cheers, Emil On 12/20/20 9:42 PM, John Goerzen wrote:Sweet! What port is this using? - John On Sun, Dec 20 2020, Christoph Lohmann wrote:Greetings comrades. Please see: https://github.com/curl/curl/commit/a1f06f32b8603427535fc21183a84ce92a9b96f7Due to the work of parazyd, curl now has support for TLS gopher.If you now use gophers:// for any URI, curl will only connect using TLSand bail, if this is not possible. Thanks parazyd for the work! It is one step to more TLS in gopher. Sincerely, Christoph Lohmann Please activate Javascript to see the full signature.