Hello everyone, during the 36c3 we organized a Tor Assembly, same as in 2017/2018. The 36c3 is the annual congress of the Germany CCC (Chaos Computer Club), which is a gathering of 17.000 people of the hacking community. I has grown a lot and people from all over the world are attending.
We also had two sessions, one was a relay operator meetup with FAQ and a presentation [1] of "Foundation of Applied Privacy" about their Exits. The other session was a Tor organizations meetup. During the organizations meetup some notes were taken and it was agreed to share those afterwards.
[1] https://appliedprivacy.net/presentations/
The following topics were discussed:
+ Concentration of Tor exit capacity in unique entities, how much of the Tor (exit) capacity should be in control of one group or person?
++ This is a recurring discussion, various people have suggested limits between 5% and 10% exit probability.
++ Frënn vun der Ënn are working on a "Tor Organization Code of Conduct" including such a self-limitation - This was only mentioned by some participants and is not first hand information.
+ Professionalization of operation and administration, challenges in finding/keeping volunteers.
++ One organization is running on "grown" infrastructure that is administrated by Perl scripts, which new volunteers are having difficulties working with.
++ Sharing documentation/code used by various organizations might be a solution, this has also been asked for at the Tor Relay Operator Meetup.
+ Why are people scared of abuse? What problem does a hosting provider face if abuse happens/is not stopped?
++ At least for most servers rented from ISPs, if you don't react to abuse email in a timely manner, they will disconnect you.
++ On a higher level, there seems to be a risk for ASNs with too much unchecked abuse.
+ Procurement of hardware
++ One organization mentioned CPU load issues if they allow port 22 exit traffic. Better hardware might help them.
++ If you can donate relatively modern server hardware to Tor organization, please consider mentioning this on tor-relays mailing list.
+ Handing over the administration of Torservers.net has not progressed very much.
++ Original post: https://lists.torproject.org/pipermail/tor-relays/2019-May/017269.html
++ One problem could be a lack of information about the type and amount of work that needs to be done.
++ Handling press inquiries has been taken over by a group of other organizations, seems to be working well.
+ IPv6
++ Some major Tor exit operator might loose their IPv4 space within the next 2-3 years, which makes progress in the IPv6 area crucial for them to continue contributing to the network.
++ The Tor Project got IPv6 funding from RIPE NCC, but in addition to the software portion (Tor Project responsibility) also operators need to take action and ensure they have IPv6 connectivity enabled on their systems.
+ BGP Routing Security
++ BGPalerter is an easy to use tool to monitor your ASN for hijacking attempts and visibility issues nitor your ASN for hijacking attempts and visibility issues https://github.com/nttgin/BGPalerter
+ Future meetings
++ Some organizations wish to be invited to the Tor meetings. People of some organizations attend the meetings aready through other means.
The meetup took 90 minutes, in the end it was decided to organize a meetup like this each year. Quarterly mumble meetings are to be held.
Some of the organizations present (in alphabetical order) were:
Artikel10 - https://artikel10.org/ Artikel 5 e.V. - https://www.artikel5ev.de/ Digitalcourage - https://digitalcourage.de/en Digitale Gesellschaft - https://www.digitale-gesellschaft.ch/ Emerald Onion - https://emeraldonion.org/meraldonion.org/meraldonion.org/meraldonion.org/mer... F3 Netze - https://f3netze.de/ Foundation for Applied Privacy - https://applied-privacy.net/ Nos Oignons - https://nos-oignons.net/ Zwiebelfreunde - https://www.zwiebelfreunde.de/
This text was composed in a pad by various people, the license of the text is CC-BY-SA 3.0, original text can be found here: https://cryptpad.fr/pad/#/2/pad/edit/eMjLydN6sIQSMbHwNwzIUHDL/
// End of protocol
I hope there is no information missing, I shared the pad and some people were working on the text in the last 3 days, please feel free to discuss the topics mentioned and also feel free to add information missing.