Skip to content

v6.0.0
Compare
Choose a tag to compare
@Enkidu-6 Enkidu-6 released this 18 Feb 12:55
· 23 commits to main since this release
v6.0.0
2133efe
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

This is major update as we are now dealing with relays that are running more than two instances of Tor.
-The rules have gone through 13 days of testing on two relays with no problems or complications.

  • A new ipset is added for relays with above 2 instances of Tor. They are now allowed one connection per ORPort.
  • Relays with Two ORPorts are kept in their own list and as usual, are allowed two connections.
  • refresh-authorities.sh is now modified to also refresh the multi-OR list.
  • remove-dual-or.sh is modified to also remove multi-or IP addresses from the block list as well as dual-OR relays.
  • The above two files will be renamed in one of the future minor updates for the sake of accuracy. The names were left unchanged to make the update to a new major version as seamless as possible.
  • conntrack.sh and conntrack-2.sh were modified to reflect multi-or relays.
  • compare.sh was modified to reflect and allow manual removal of multi-or relays from the block list as well.
  • A new script dynamic.sh is now added for operators who have a dynamically changing IP address.
  • Some cosmetic changes
  • A few bug fixes.
  • No need to change current cron jobs as there are no file name changes.
  • Simply use update.sh to update your rules with no downtime.

Finally, for the sake of transparency, at the time of this release there are only 69 IP addresses running more than two instances of tor, out of which 52 are Exit relays with zero middle and zero Guard probability. However I believe people must have the option so they can choose for themselves, hence the new rules.

Cheers.

Assets 2
Loading