Activity
Background info also here: dev-ml thread.
#9854 (moved) is also quite relevant here, despite the fact that it's already closed. It contains a lot of background.
We should consider doing this (stop sanitizing contact information from bridge descriptors) when we reprocess the bridge descriptor archive the next time.
Minor remark: OnionTip (now TorTip) would be able to use bridge contact information to list bridges and distribute bitcoins to bridge operators. Not sure if that helps a lot, but it's another reason to do it. (Not saying there are no reasons against it, but let's collect all reasons before we decide.)
After looking at the spec https://gitweb.torproject.org/torspec.git/tree/bridgedb-spec.txt#n55
I noticed that the bridge descriptor does not even contain contactinfo?
So it is not there and can not be published?
Replying to cypherpunks:
After looking at the spec https://gitweb.torproject.org/torspec.git/tree/bridgedb-spec.txt#n55
I noticed that the bridge descriptor does not even contain contactinfo?
So it is not there and can not be published?
That's not the bridge descriptor specification, it's the BridgeDB specification. BridgeDB is a bridge distribution service. Bridge descriptors are produced by the Tor daemon just like relay descriptors. They do contain contact information.
Tweak the summary a bit.
FWIW, there's now a specification for sanitized bridge descriptors.
Trac:
Summary: bridge ContactInfo information (less sanitization) to Stop sanitizing contact information from bridge descriptors