Maybe because there isn't a known solution?
CSAM is still distributed on the clearnet too... why isn't there a "solution" for that too?
So far the only solutions people seem to have come up with is mass surveillance, and that's not an option.
CSAM is still distributed on the clearnet too... why isn't there a "solution" for that too?
So far the only solutions people seem to have come up with is mass surveillance, and that's not an option.
Did you know that the Tor Project allows exit nodes to filter based on the clear internet IP. So filtering is ok.
However, if a relay refuses to service an onion site directory look up, it will be banned by the Directory Authority. They could allow this today. But they don’t. That’s the simple solution. No surveillance. Not back door. No less privacy for everyone else.
edit: This is easy to confirm. I’m not asking anyone to trust me.
> For the Tor network, Onion Services can alleviate the load on exit nodes, since it's connections don't need to reach the exits.
Also:
> Directory Authority.
"These authorities are operated by trusted organizations or individuals with a strong commitment to the principles of privacy, security, and network neutrality."
Emphasis on neutrality... it's not the job of network operators to police the sites people can and can't access, this is exactly why many people use Tor in the first place.
> They could allow this today. But they don’t.
Speaking for onion services... no, they cannot, because the entire design of the tor network prevents this in the first place. No relay in the circuit knows the final destination because it is encrypted multiple times (like an onion) and each hop can only see where it needs to go next, not what the destination is.
Because the network was explicitly designed to not allow this... otherwise it becomes subject to censorship, which is one of the main goals they try to prevent.
The (onion) address itself is never transmitted in plaintext through the Tor network... when you access an onion site, your Tor client encrypts the traffic multiple times, literally like an onion. No relay in the circuit knows the final destination.
Conversely, even if the official project implemented an onion blacklist, a fork would quickly appear to remove it. And node operators would likely prefer that one.
Anyone with any sense understands that introducing a node blacklist creates the capability to expand the use of that blacklist in the interest of political and/or military censorship. The Tor project, Tor devs, and node operators are adamantly opposed to any such censorship capabilities. Therefore it will not happen, period.
Edit: on second look I can see how you could think it was. I’m just proposing that if you run a node you be allowed to not become a rendezvous point for onion sites.
That's simply not true. Exit operators who intentionally block websites are flagged as bad relays.
https://community.torproject.org/policies/relays/expectation... https://gitlab.torproject.org/tpo/network-health/team/-/wiki...
https://support.torproject.org/relay-operators/exit-policies...
The documents you referred to just say you need to honor your own exit policy.
Specifically, it would be easy to add code to hsdir functionality to deny requests for onion sites that are known to be related to csam. Those sites could be announced by the DAs as part of the consensus file, for example. The Tor Project currently lets exit nodes filter by IP address as long as they announce that in their config; this new functionality is of the same kind in the abstract. This change would not be a backdoor. It’s not going to weaken the privacy of anyone using Tor.
The current setup is an extremist position that children who have been abused are not deserving of privacy. It’s a position that all information deserves to be free even if that information is very clearly harmful to others and has no positive benefit to society. One can have that opinion but you won’t find many (outside of this thread) that agree.