On 7/1/25 05:38, atari … via tor-relays wrote:
Hej,
they are all green again on metrics ;)
Your bridges showing offline from time to time is related to not exposing your ORPort (which is highly recommended). See these 2 tickets:
https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/129 https://gitlab.torproject.org/tpo/web/community/-/issues/329
To be clear, it is strongly strongly recommended that WebTunnel bridges do not expose their ORPort. Doing so could make them vulnerable to enumeration through port scanning, which isn't ideal.
Exposing it could allow malicious actors to set up middle relays that port scan clients connecting to them looking for the ORPort, making it easier to identify and compile a list of all the bridges.
If AssumeReachable 1 is now sufficient for obfs4, then neither type of bridge should be exposing their ORPort. The non-Docker guides on torproject.org should be updated to reflect that.
If you can use your bridge and its shown as “webtunnel: functional” when you check here: https://bridges.torproject.org/status?id=$YOURFINGERPRINT everything should be fine.
Best regards, atari _______________________________________________ tor-relays mailing list -- tor-relays@lists.torproject.org To unsubscribe send an email to tor-relays-leave@lists.torproject.org