Today marks the end of Tor version 0.4.0.x
Currently over 10% of the Tor network is running on end-of-life tor releases.
This is bad.
This is the list of affected relays:
https://nusenu.github.io/OrNetStats/eolrelays
tor v0.4.0.x will reach its end-of-life in under 3 weeks on 2020-02-02.
There are currently over 400
relays still using that version.
They make up >10% of the tor network's guard capacity
and >7% of the exit capacity.
List of affected relays:
https://metrics.torproject.org/rs.html#search/version:0.4.0.
It is proven! I am nusenu on Keybase: https://keybase.io/nusenu/sigchain#3baf77007e4845ddd30b2f738bf2de0d261e774497143e5303fd34dd35a6a26a0f
Their reply to my appeal:
"Hello,
We’re writing to let you know that your account has been suspended due to multiple or repeat violations of our rules.
Please do not reply to this email, or send us new appeals for this account as we won’t monitor them.
Thanks,
Twitter"
Why I disappeared from Twitter
https://medium.com/@nusenu/why-i-disappeared-from-twitter-8e9b48423d98
Be mindful of the powers that platforms have over your ability to freely communicate!
Yesterday over 250 new Tor exit relays joined the network.
64 are still running. They are located in AS208870 upstream via AS20473 Choopa, LLC.
This triggered a few Sybil attack detectors
https://nusenu.github.io/OrNetRadar/2020/01/06/a11.html
Related RIPE DB entries:
https://gist.github.com/nusenu/bd2cce0296adb054d35b1fce9c01050f
relayor v20.0.0 got released
The Growing Problem of Malicious Relays on the #Tor Network
https://medium.com/@nusenu/the-growing-problem-of-malicious-relays-on-the-tor-network-2f14198af548
During the last 3 weeks the amount of #RPKI unreachable IPv4 address space increased by over 1000 /24 blocks
mainly due to a single /14 prefix in CN
https://nusenu.github.io/RPKI-Observatory/unreachable_rir-v4.html
Over 700 relays run end-of-life tor releases. They make up 3.8% of the Tor network's capacity.
https://nusenu.github.io/OrNetStats/#end-of-life-relays-share
So Twitter suspended my account without providing any reasoning. It is probably related to using Tor Browser but that used to work for years without major issues.
I asked them to unlock the account, lets see how this goes.
Over a year ago I looked into who controls Tor's DNS traffic, this is how things changed since then:
Routing Security and Tor:
How vulnerable is the Tor Network to BGP Hijacking Attacks?
https://medium.com/@nusenu/how-vulnerable-is-the-tor-network-to-bgp-hijacking-attacks-56d3b2ebfd92
Who controls #Tor's DNS traffic?
An Analysis of the @torproject DNS Landscape.
https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca
I'd like to have #DNSSEC indicators (among other new items) on the TorAtlas page of exit relays, lets see what the tor-metrics team thinks about it
Dear @torproject exit relay operators,
only 74% of the tor exit capacity does #DNSSEC validation, let's increase that figure to >90%. Please look into your DNS setup if your ContactInfo string is mentioned on this page:
Want to help grow the torproject network by adding #Tor relays? This guide will help you get going:
https://blog.torproject.org/new-guide-running-tor-relay
(joined blog post with flexlibris)
If you need help the tor-relays mailing list is happy to answer your questions
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I just released relayor v0.3.1 - the ansible role for #Tor relay operators.
It comes with support for:
#FreeBSD / #HardenedBSD
#Debian / #Ubuntu
#CentOS / #Fedora
#OpenBSD
https://github.com/nusenu/ansible-relayor/releases
This is an important new #Tor feature for relays and the entire network: The new denial of service mitigation got merged into the MASTER branch.
If you can't wait for the next alpha release to try it out, you might be able to use provided nightly builds if you use a debian-based OS.
https://deb.torproject.org/torproject.org/dists/
#privacy infrastructure