Replying to Avatar Ingwie Phoenix (aka. birb)

It's alive in tor now too: ws://m2swjvhhbxcctnesbwwkqruwlz2fmlbi2u5cyulp7gzzi7pvjj42otqd.onion

That said, since .onion totally allows TLS even via let's encrypt, I will probably put this behind Caddy later and enable HTTPS support. But: It resolved and responded WAY faster! And immediately too, i2p actually needed two tries to get the first connection to work.

Will do the Caddy linkage in a bit; curious to see how it's auto TLS handles onions.
Avatar
Rif'at Ahdi R 2y ago

Oh, nice, you can probably add them into 0xtr onion relay repository list 👀

https://github.com/0xtrr/onion-service-nostr-clients

Why do you want to add extra TLS? Is it for benchmark? I think it only add extra overhead in encryption while only gain minimal benefit. Nostr relay seems doesn't really need double encryption because its data already protected with signature 😅

https://blog.torproject.org/tls-certificate-for-onion-site/

Did LetsEncrypt announce their support for .onion TLS certificates? Probably i missed them, i thought it was still in draft?

https://acmeforonions.org/

Reply to this note

Please Login to reply.

Discussion

Avatar
Ingwie Phoenix (aka. birb) 2y ago

I am just curious about adding TLS...because, because. x) Curiosity, trying things out, see what sticks and what breaks. I am working on a project that interops with i2p and tor - so I need to get my knowledge together. ^^

Thanks for the pointers, will give it a peek!

Avatar
Rif'at Ahdi R 2y ago

Oh, i see. It's fine if you want to do some experiments. Please, keep your curiousity, don't kill it. 😄

It will be helpful especially if you documented all the experiments in some notes/blogs/posts as references for other people with similar cases. 🙂