#toroperators — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #toroperators, aggregated by home.social.
-
Our lead relay engineer @alexhaydock has increased our stateless #Tor exit relay deployment to 96! (+1 because of the new #RISCV bare-metal node, +1 other we redeployed due to a silly spelling error). We're stress testing our three AMD Epyc 7402P servers that use #Proxmox.
Each one of the 96 Tor exit nodes are diskless Unified Kernel Images, 56MB in total size, using @alpinelinux's alpine-make-rootfs with an absolutely bare minimum number of packages. We'll be publishing more about our new architecture and configuration soon.
#AlpineLinux #privacy #anonymity #AntiCensorship #AccessToInformation #TorOps #TorOperators
-
Our lead relay engineer @alexhaydock has increased our stateless #Tor exit relay deployment to 96! (+1 because of the new #RISCV bare-metal node, +1 other we redeployed due to a silly spelling error). We're stress testing our three AMD Epyc 7402P servers that use #Proxmox.
Each one of the 96 Tor exit nodes are diskless Unified Kernel Images, 56MB in total size, using @alpinelinux's alpine-make-rootfs with an absolutely bare minimum number of packages. We'll be publishing more about our new architecture and configuration soon.
#AlpineLinux #privacy #anonymity #AntiCensorship #AccessToInformation #TorOps #TorOperators
-
Our lead relay engineer @alexhaydock has increased our stateless #Tor exit relay deployment to 96! (+1 because of the new #RISCV bare-metal node, +1 other we redeployed due to a silly spelling error). We're stress testing our three AMD Epyc 7402P servers that use #Proxmox.
Each one of the 96 Tor exit nodes are diskless Unified Kernel Images, 56MB in total size, using @alpinelinux's alpine-make-rootfs with an absolutely bare minimum number of packages. We'll be publishing more about our new architecture and configuration soon.
#AlpineLinux #privacy #anonymity #AntiCensorship #AccessToInformation #TorOps #TorOperators
-
Our lead relay engineer @alexhaydock has increased our stateless #Tor exit relay deployment to 96! (+1 because of the new #RISCV bare-metal node, +1 other we redeployed due to a silly spelling error). We're stress testing our three AMD Epyc 7402P servers that use #Proxmox.
Each one of the 96 Tor exit nodes are diskless Unified Kernel Images, 56MB in total size, using @alpinelinux's alpine-make-rootfs with an absolutely bare minimum number of packages. We'll be publishing more about our new architecture and configuration soon.
#AlpineLinux #privacy #anonymity #AntiCensorship #AccessToInformation #TorOps #TorOperators
-
Our lead relay engineer @alexhaydock has increased our stateless #Tor exit relay deployment to 96! (+1 because of the new #RISCV bare-metal node, +1 other we redeployed due to a silly spelling error). We're stress testing our three AMD Epyc 7402P servers that use #Proxmox.
Each one of the 96 Tor exit nodes are diskless Unified Kernel Images, 56MB in total size, using @alpinelinux's alpine-make-rootfs with an absolutely bare minimum number of packages. We'll be publishing more about our new architecture and configuration soon.
#AlpineLinux #privacy #anonymity #AntiCensorship #AccessToInformation #TorOps #TorOperators
-
8 days in and already up to 2.14 Gbps advertised bandwidth!
-
do Tor operators outside of the EU need to have, and publicly disclose, an EU rep because of DSA? ("mere conduit")
-
We're excited to have published a new @torproject WebTunnel bridge hosted by disobey.net!
Details are on https://emeraldonion.org/bridges
#Tor #TorOperators #anticensorship #privacy #anonymity #WebTunnel #obfs4 #infosec #cybersecurity #encryption #cryptography
-
boop boop
back in the top 10!
our tor exit relays seem to be more performant after doubling the RAM from 64GB to 128GB
#tor #torops #TorOperators #privacy #censorship #anonymity #infosec #cyber #cybersecurity
-
all 40 of our exit relays are back online this evening. we visited the datacenter and found the servers completely frozen.
on a positive note, all three of our Epyc HPEs have been upgraded to 128GB of RAM!
we'll be bumping up each server's relay count to 30 soon (currently 20 each). one of them has been out of service for a while, we'll be getting it back up with relays too, for a total of 90 exit relays.
#tor #privacy #censorship #anonymity
#TorOperators #cybersecurity #infosec -
Tor Project documents a list of Relay Associations:
https://community.torproject.org/relay/community-resources/relay-associations/
#tor #TorOperators #privacy #network #security #anonymity #censorship
-
On this #GivingTuesday, we are launching 10 public @torproject #obfs4 bridges!
We don't expect these bridges to be particularly good at evading #government #censorship since they are in the same IPv4 /24 subnet as our exit relays. Countries like China and Russia undoubtably already block our subnet. However, we think they are a trustworthy (and fast) guard node when configured.
If you'd like to try one of our bridges, we have published them here:
https://bridge.emeraldonion.org
Please consider #donating to U.S. 501(c)(3) tax-deductible #nonprofit Tor network operators before the end of the year:
Emerald Onion: https://emeraldonion.org/donate/
Calyx Institute @calyxinstitute: https://members.calyxinstitute.org/donate
Stormy Cloud @stormycloud: https://stormycloud.org/donate/
Riseup @riseup: https://riseup.net/donate
(if there are any other that we missed, please let us know!)
#privacy #anonymity #TorOperators #network #security #obfs4proxy #pluggabletransports
-
From @torproject: #tor stable release 0.4.7.15 and 0.4.8.6
"We are today releasing both 0.4.7.15 and 0.4.8.6 with an important fix for onion services regarding congestion control and its reliability. We strongly encourage all onion service operators to upgrade as soon as possible to the latest stable that is the 0.4.8.x series.
We also address the issue with the annoying “compression bomb” log message that some relay operators have been noticing a lot lately.
Important to remember that we are expecting to end of life the 0.4.7.x series in a couple of months (likely around November) after the majority of the network has migrated and Tor Browser stable no longer ships it. That being said, please upgrade to the 0.4.8.x latest stable as soon as you can."
From forum post: https://forum.torproject.org/t/stable-release-0-4-7-15-and-0-4-8-6/9292
0.4.8.x Release notes: https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.8/ReleaseNotes
-
We've updated our 40 exit relays to @torproject 0.4.8.5, after building from source!
We'll soon be upgrading @nusenu's #AnsibleRelayor to v23.2.0 (https://mastodon.social/@nusenu/110968476072489198), but we need to re-deploy our offline system from which it runs
-
#Tor stable release 0.4.8.5
"We are quickly releasing a new version after last week stable release in order to fix #BSD compilation issues and an annoying BUG() stacktrace in the logs for relay operators.
As usual, we strongly encourage everyone to upgrade to this version as soon as possible."
Forum post: https://forum.torproject.org/t/stable-release-0-4-8-5/8996
Release notes: https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.8/ReleaseNotes
Tarballs: https://dist.torproject.org
-
since the #debian/ #ubuntu repos are so behind in updates, we've built @torproject 0.4.8.4 from source, and all relays have been restarted
-
Tor has a new Stable release, 0.4.7.14
"This version fixes several minor bugfixes and one major bugfix affecting vanguards (onion service). And as usual, we do recommend to upgrade to this version.
Nothing more to say about this release. Not a big one ;)."
Release notes: https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.7/ReleaseNotes
#Tor operators should update!
-
Randomly, we are 3rd in the world right now for #Tor exit probability (4.9118%)
Advertised bandwidth is 1,907 MiB's but our real throughput has peaked at 5.2 Gbps symmetrical
-
Apparently #tor 0.4.7.11 was released 21 days ago and has a strong recommendation for #TorOperators to update, re: #DDoS attacks on the network:
-
.@torproject Tor 0.4.7.11 has been released
tor (0.4.7.10-1~jammy+1 => 0.4.7.11-1~jammy+1)