4 ms·
It's a nice but something more efficient would be some automated way to discover the onion services for domain while staying in the onion network. Like being ab
by Buetol 10y ago
It's a nice but something more efficient would be some automated way to discover the onion services for domain while staying in the onion network. Like being able to have onion domains like backports.debian.org.onion or having some sort of protocol upgrade when accessing backports.debian.org with a Tor-capable client.
- xg15 10y agoBut how would that work? You'd have to have some kind of bootstrap hidden service which would essentially act as a DNS or search engine. But as soon as that service exists, you have again a single point of failure.
- ikeboy 10y agoRequire them to use the same cert as for their main site, so a CA compromise is required. Also have it published in certificate transparency databases, so a targeted attack is impossible.
- xena 10y agoYou can have multiple nodes broadcasting the same hidden service ID. The name collision this causes will let you use the tor network as a load balancer.
- ashitlerferad 10y agoSome sort of DNS attribute might work.
- Buetol 10y agoOn the same topic, there's a fork of HTTPS Everywhere to do this exact same use-case: https://github.com/chris-barry/darkweb-everywhere https://github.com/chris-barry/darkweb-everywhere
- breakingcups 10y agoHow about a seperate DNS-record, like CNAME only pointing to an onion address? (I'm still pissed most new DNS records abuse TXT to improve adoptin speed by the way)