You don’t need to trust the relays. Your client checks signatures and proof of work.

Reply to this note

Please Login to reply.

Discussion

I know. It's not about trusting relays. Its about making sure you are talking to the right relay. If you set up your private party relay, you must take additional protections to make sure you are talking to your machine.

Governments can modify DNS entries as well as the pure IP graph, making a different computer reply in your relays behalf, adding a censorship filter, for instance.

I see. Yeah DNS is not reliable. But, tor should work.

Doesn’t https / .onion take care of that?

Http and https definitely not. I am not sure about onion. For https, the only way to avoid gov takeover is to check if the certificate is using the exact keys of the original party. Beyond the usual https checks.

Yes you’re right. Tor fixes this. Look into it, I’m pretty sure we already have a few tor relays too. But it’s easy to set up a private one.

I am not confident Tor doesn't allow a Stateless relay to be placed between you and your own Tor relay. For me, the safe way is to hardcode the relay's pubkey in the app to make sure only that key can decode incoming payloads and the relay only take encrypted msg from that key

You don’t know how tor works

Probably. But I also can't find proof that somebody can't put a server in between my phone and my server. https://security.stackexchange.com/questions/215155/how-does-tor-protect-against-mitm-attacks-between-the-client-and-relay-nodes

I remember a long time ago using a VPN app and setting it up to use TOR, essentially tunneling all connections. would this help in this case?

🤔 maybe you’re right