Live data from Hacker News

Show HN: Running the second public ODoH relay

numa.rs

31–40 of 50 posts

Re: Show HN: Running the second public ODoH relay

#31

Pretty cool to see someone actually running public ODoH infra instead of just talking about privacy in theory. I'm just wondering what the biggest operational pain has been so far running a public relay.

honestly, nothing major, just deployed the docker-compose to a hetzner $5 instance https://github.com/razvandimescu/numa/tree/main/packaging/re...

then submit a pr to Frank https://github.com/DNSCrypt/dnscrypt-resolvers/blob/master/v...

Re: Show HN: Running the second public ODoH relay

#32

Earlier quoted context omitted.

It means you can use a decently fast DNS server like Cloudflare without the major privacy problems of using Cloudflare. Or DNS4EU, or any non-ISP DNS server really. Your ISP snooping on you with SNI logging is something people using normal ISPs don't need to worry about, but feeding all your data into a profit-driven company is.

> something people using normal ISPs don't need to worry about It doesn't matter which ISP you're using if the cables are tapped, which they pretty much are.

If you piss off any government enough that you suspect your wires may be tapped, ODoH will not save you and TOR probably will not do much better.

If you live in a place with omnipresent government monitoring (China/Iran/etc.), there is no solution. Any solution to getting wiretapped with a legal order will almost certainly be an extra charge the day you do get arrested.

Re: Show HN: Running the second public ODoH relay

#33
post #24
post #3

What’s the selling point of ODoH given the low uptake of ECH which means the name of the server you’re talking to is given away anyway?

What's the selling point of locking your front door given that you have an easily breakable window nearby?

It's more like closing the blinds while your frontdoor is wide open.

Re: Show HN: Running the second public ODoH relay

#34

Earlier quoted context omitted.

> something people using normal ISPs don't need to worry about It doesn't matter which ISP you're using if the cables are tapped, which they pretty much are.

Please don’t be intentionally tone-deaf. “a nation-state can track my shit therefore it’s not with doing” is a silly, silly, silly approach to security, and does not speak to the concerns of the vast majority of even privacy-focused people.

[deleted]

Re: Show HN: Running the second public ODoH relay

#35
post #3

What’s the selling point of ODoH given the low uptake of ECH which means the name of the server you’re talking to is given away anyway?

By that logic, someone else would ask "what's the point of ECH since that data will just leak via DNS?" and then neither technology would ever roll out. Deploying this now despite that is exactly how you fix that chicken-and-egg problem.

Re: Show HN: Running the second public ODoH relay

#36
this is what i was looking for. seems like a truly zero conf alternative to technetium hope it works nice on mac even with docker. can it run as a service? any future integration planned with tailscale? it would be nice to have a pluggable system so this can be used instead of tsdproxy as well. maybe a connection to docker socket is necessary to have a service discovery feature.

Re: Show HN: Running the second public ODoH relay

#37
post #27

What is the end-game for the private TLD? Is this going to turn into some cryptocurrency thing?

sovereign naming without ICANN or registrars - pkarr through DHT (not blockchain)

That's really great. I apologize for my initial cynicism. How can you address something like namesquatting if it's first-come?

Re: Show HN: Running the second public ODoH relay

#38

this is what i was looking for. seems like a truly zero conf alternative to technetium hope it works nice on mac even with docker. can it run as a service? any future integration planned with tailscale? it would be nice to have a pluggable system so this can be used instead of tsdproxy as well. maybe a connection to docker socket is necessary to have a service discovery feature.

actually that is exactly how i am currently running it - dogfooding from my Mac

sudo numa install handles launchd, numa then becomes tailscale's fallback resolver

docker socket service discovery - on the roadmap

Re: Show HN: Running the second public ODoH relay

#40
post #18
post #16

Earlier quoted context omitted.

The relay sees IP + ciphertext, the target sees question + relay's IP. No single party gets both

What if the relay and target are being operated by the same provider? The relay controls where the question is sent right? They can collude?

If relay and target are operated by the same provider, there is no collusion. Collusion occurs between 2+ parties. You have stipulated that they are the same party.
Post reply on HN