#torbridge — Public Fediverse posts

Use bridge relays if Tor is blocked in your region.

#TorBridge #CensorshipResistance #AccessControl

DeadSwitch Protocol - Dark Mirror Relays: Obscuring the Path #DarkMirrorRelays #DeadSwitchProtocol #NetworkObfuscation #ChainedVPN #TorBridge #CyberAnonymity #OPSEC #TomITCafe

http://tomsitcafe.com/2025/05/29/deadswitch-protocol-dark-mirror-relays-obscuring-the-path/

DeadSwitch Protocol - Dark Mirror Relays: Obscuring the Path #DarkMirrorRelays #DeadSwitchProtocol #NetworkObfuscation #ChainedVPN #TorBridge #CyberAnonymity #OPSEC #TomITCafe

http://tomsitcafe.com/2025/05/29/deadswitch-protocol-dark-mirror-relays-obscuring-the-path/

DeadSwitch Protocol - Dark Mirror Relays: Obscuring the Path #DarkMirrorRelays #DeadSwitchProtocol #NetworkObfuscation #ChainedVPN #TorBridge #CyberAnonymity #OPSEC #TomITCafe

http://tomsitcafe.com/2025/05/29/deadswitch-protocol-dark-mirror-relays-obscuring-the-path/

@torproject It seems to be quite a similar problem as the user "NewBoard" had in this thread: https://tor.stackexchange.com/questions/23118/why-does-tor-metrics-show-my-bridge-offline-after-a-few-days
Is there anything I can do without restarting my bridge? 3/3
#TorBridge

@torproject I have been running a #TorBridge for 10 months now. At the beginning I restarted it too often (after every kernel update) so that I didn't get many users. Finally, I decided to leave it alone for a while and only check bridge-stats and Metrics. Both showed me at the beginning of last December an explosion of users, especially from on central Asian country. I was happy but almost instantly Metrics showed me that my bridge was down (red dot on Metrics page) which it wasn't. 1/

Ich hab noch ein weiteres Problem mit meiner #TORbridge, das Updates verhindert:
sudo apt update hat eine Fehlermeldung zur Folge: "Die folgenden Signaturen waren ungültig: EXPKEYSIG 74A941BA219EC810 deb.torproject.org archive signing key"
Ich habe dann
sudo apt-key adv --keyserver keys.gnupg.net:80 --recieve-keys 74A941BA219EC810 eingegeben. Resultat:
gpg: Empfangen vom Schlüsselserver fehlgeschlagen: No keyserver available

Hab seit kurzer Zeit das Problem, dass meiner #TORbridge die Besucher fern bleiben. Die Logs sagen seither auch "Unexpected path length 4 for exit circuit XYZ (eine Zahl), purpose 14 (oder auch mal 5)". Weiß jemand, was hier plötzlich falsch läuft?