As part of our ongoing effort to reimplement BridgeDB, we now have a bridge status page that shows if a bridge's pluggable transports work:
https://bridges.torproject.org/status?id=FINGERPRINT
FINGERPRINT is your bridge's fingerprint or its hashed fingerprint -- either works.
The backend tests bridges every 18 hours by making a tor process fetch the bridge's descriptor. Tor bridges will soon log a URL pointing to this status page: https://gitlab.torproject.org/tpo/core/tor/-/issues/30477
As of today, 89% of all pluggable transports work.
Cheers, Philipp
On 11.01.2021 21:59, Toralf Förster wrote:
On 1/11/21 9:03 PM, Philipp Winter wrote:
FINGERPRINT is your bridge's fingerprint or its hashed fingerprint -- either works.
for public bridges ;-)
Bridges (PublishServerDescriptor 1 + BridgeDistribution none) work.
Completely private bridges (PublishServerDescriptor 0 + BridgeDistribution none) can look here: https://bridges.torproject.org/scan/
Would be nice if BridgeDB someday outputs IPv6 obfs bridges ;-)
On Tue, Jan 12, 2021 at 10:03:52PM +0100, lists@for-privacy.net wrote:
On 11.01.2021 21:59, Toralf Förster wrote:
On 1/11/21 9:03 PM, Philipp Winter wrote:
FINGERPRINT is your bridge's fingerprint or its hashed fingerprint -- either works.
for public bridges ;-)
Bridges (PublishServerDescriptor 1 + BridgeDistribution none) work.
Yes, that's because the backend needs a bridge's descriptor but doesn't care about its distribution method.
Completely private bridges (PublishServerDescriptor 0 + BridgeDistribution none) can look here: https://bridges.torproject.org/scan/
Note that this service only tests the target's TCP port. The port may be reachable but the bridge may still be dysfunctional. The /status page actually fetches the target's descriptor, which gives you more assurance that the bridge actually works.
tor-relays@lists.torproject.org
-
lists＠for-privacy.net -
Philipp Winter -
Toralf Förster