> rewriting onion proxies
Though it should be noted that if users already
can't get their own simple human link and
bookmark usage right... they're probably not
going to get any higher level naming or
authority config and usage right either.
___
tor-dev
> sign a
> self-signed tls certificate with your Onion Service's hs_ed25519_secret_key
> and Tor Browser trusting the tls certificate based on this signature
- In unlikely case tor crypto fails or breaks, e2e TLS
is good there.
- An admin might terminate onions on one box, and
forward the plaintex
"That said multiple layers of crypto cannot hurt, Facebook for example
uses this approach."
The first part is not strictly true. For the second part, FB uses an
identity-verified EV cert from a known CA to let their users confirm
their identity, not for increased encryption. Creating an onion
serv
Hi everyone,
So I have an idea which may or may not be a possibility. Currently Tor Onion
Services do not need HTTPS since they are already end to end encrypted. That
said multiple layers of crypto cannot hurt, Facebook for example uses this
approach. So I have the idea of some sort of mechanis
