Re: [tor-relays] A call to arms for obfuscated bridges

[Nikolaus Rath <Nikolaus@xxxxxxxx>]

George Kadianakis <desnacked@xxxxxxxxxx> writes:
> Looking into BridgeDB, we have 200 obfs2 bridges, but only 40 obfs3
> bridges: this means that we need more people running the new Python
> obfsproxy! Upgrading obfsproxy should be easy now, since we prepared
> new instructions and Debian/Ubuntu packages. If you run Debian or
> Ubuntu check out these instructiosn:
> https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en
> otherwise use these:
> https://www.torproject.org/projects/obfsproxy-instructions.html.en
> (and make sure your pip is upgraded so that it uses HTTPS [4])

I read about this on Arstechnica and wanted to help out. I think I got a
bridge running. But how do I check? The logs just say:

Apr 19 19:03:26.000 [notice] Registered server transport 'obfs3' at '0.0.0.0:xxxx0'
Apr 19 19:03:26.000 [notice] Registered server transport 'obfs2' at '0.0.0.0:xxxx'
Apr 19 19:03:27.000 [notice] Guessed our IP address as xxxx (source: 93.114.43.156).
Apr 19 19:03:27.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 19 19:03:27.000 [notice] Bootstrapped 100%: Done.
Apr 19 19:03:27.000 [notice] Now checking whether ORPort xxxx:443 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Apr 19 19:06:30.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Apr 19 19:11:35.000 [notice] Performing bandwidth self-test...done.

...no self-test for obfs?

Best,

   -Nikolaus

-- 
 ÂTime flies like an arrow, fruit flies like a Banana.Â

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays