💾 Archived View for rawtext.club › ~sloum › geminilist › 001282.gmi captured on 2020-09-24 at 01:59:17. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Sean Conner sean at conman.org
Wed Jun 3 01:59:00 BST 2020
- - - - - - - - - - - - - - - - - - -
It was thus said that the Great Petite Abeille once stated:
On Jun 2, 2020, at 22:59, plugd <plugd at thelambdalab.xyz> wrote:
Is this really necessary?
TLS in general? A minimum version of it? Not really.
But mandating a secure channel of sort is value added.
That said, mandating TLS only is perhaps counterproductive.
After all, how do I run Gemini over wireguard now? With TLS on top?
Because the spec forces me to? Oh, my...
Wireguard is a VPN implementation, not specifically a protocol. And aswith other people who have questioned the use of TLS, show us animplementaion. Get a Gemini server working over wireguard. Or bothwireguard *and* TLS. Because as it is, I have no idea how to go about this,nor any easy means to test it.
Perhaps Gemini should mandate a secure transmission channel, and then
define a profile of it in the specification., say TLS vs TLS
= 1.3 vs
wireguard vs whatnot.
Again, the devil is in the details, and we need some more details aboutthis.
-spc (And then convince the gopher people who are working hard to get TLS working that *that* protocol ... )