[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9264 [BridgeDB]: Problem with transport lines in BridgeDB's bridge pool assignment files



#9264: Problem with transport lines in BridgeDB's bridge pool assignment files
--------------------------+----------------------------
     Reporter:  karsten   |      Owner:  isis
         Type:  defect    |     Status:  needs_revision
     Priority:  major     |  Milestone:
    Component:  BridgeDB  |    Version:
   Resolution:            |   Keywords:
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+----------------------------

Comment (by isis):

 Replying to [comment:26 isis]:
 > ''This was already stated on IRC, but for the record:''
 >
 > Thanks for adding those unittests! :) Have you looked at
 [http://falcao.it/sure/reference.html sure]? It's perfect for testing the
 parsers; I'vehttp://falcao.it/sure/reference.html used it in
 [https://gitweb.torproject.org/user/isis/bridgedb.git/blob/HEAD:/lib/bridgedb/test/test_parse_networkstatus.py#l116
 a couple test files] already, i.e.:
 >
 > {{{
 > this(port).should.be.ok
 > this(port).should.be.a(networkstatus.addr.PortList)
 > }}}
 >
 > It's pretty terse and readable, plus the crazy syntax made writing tests
 more entertaining. (You don't have to use it, this is just a general "hey
 dude! check out this neat thing!" :D )
 >
 > sysrqb, in your bug9264_rebased_0 patches, I think something broke
 Bridge.getConfigLine() or another related function. Testing the email
 server and HTTPS interface resulted in:
 >
 > {{{
 > Feb 08 06:57:12 [DEBUG] fa25ed11b3a7cf918de82460959b81d50b40a4df
 supports 2 transports
 > Feb 08 06:57:12 [DEBUG] 590e93e84ac43a994392d402a7ca103ab2e2ad5c
 supports 2 transports
 > Feb 08 06:57:12 [DEBUG] 83158cbfb8e76f9f782c706cd88f0d519a270867
 supports 2 transports
 > Feb 08 06:57:12 [DEBUG] Saving state to:
 '/home/isis/code/torproject/bridgedb/run-manual/bridgedb.state'
 > Feb 08 06:57:13 [DEBUG] Opening GPG keyfile
 gnupghome/TESTING.subkeys.sec...
 > Feb 08 06:57:13 [INFO] GPG Key with fingerprint
 318A83A975C91BD4538C317C4A792354FA079716 imported
 > Feb 08 06:57:13 [INFO] Testing signature created with GnuPG key...
 > Feb 08 06:57:13 [INFO] Starting reactors.
 > Feb 08 07:03:02 [DEBUG] > Received: BridgeDB
 > Feb 08 07:03:02 [DEBUG] > From: isis@xxxxxxxxx
 > Feb 08 07:03:02 [DEBUG] > To: bridges@xxxxxxxxx
 > Feb 08 07:03:02 [DEBUG] > Subject: testing
 > Feb 08 07:03:02 [DEBUG] >
 > Feb 08 07:03:02 [DEBUG] > get bridges
 > Feb 08 07:03:02 [INFO] Got a completed email; deciding whether to reply.
 > Feb 08 07:03:02 [INFO] Attempting to return for 3 bridges for
 isis@xxxxxxxxxxxx
 > Feb 08 07:03:02 [DEBUG] Cache hit frozenset([<function
 filterBridgesByIP4 at 0x17f58c0>])
 > Feb 08 07:03:02 [DEBUG] Returning 3 bridges from ring of len: 356
 > Feb 08 07:03:02 [DEBUG] Got duplicate bridge
 'fa179ed482ff4096a2548db2fbdbc7046abe093d' in main hashring for position
 'f8f6fd62d22b6d29e684b0149eff7ef7a7aaf177'.
 > Feb 08 07:03:02 [DEBUG] Email body:
 > Content-Type: text/plain
 > From: bridges@xxxxxxxxxxxxxx
 > To: isis@xxxxxxxxx
 > Message-ID:
 <20140208070302.8823.222990448.0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
 > Subject: Re: testing
 > Date: Sat, 08 Feb 2014 07:03:02 +0000
 >
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA512
 >
 > [This is an automated message; please do not reply.]
 >
 > Here are your bridge relays:
 >
 >   None
 >   None
 >   None
 >
 > Bridge relays (or "bridges" for short) are Tor relays that aren't listed
 > in the main directory. Since there is no complete public list of them,
 > even if your ISP is filtering connections to all the known Tor relays,
 > they probably won't be able to block all the bridges.
 >
 > To use the above lines, go to Vidalia's Network settings page, and click
 > "My ISP blocks connections to the Tor network". Then add each bridge
 > address one at a time.
 >
 > Configuring more than one bridge address will make your Tor connection
 > more stable, in case some of the bridges become unreachable.
 >
 > The following commands are also supported:
 >
 >   ipv6 : request ipv6 bridges.
 >   transport NAME : request transport NAME. Example: 'transport obfs2'
 >
 > Another way to find public bridge addresses is to visit
 > https://bridges.torproject.org/. The answers you get from that page
 > will change every few days, so check back periodically if you need more
 > bridge addresses.
 >
 > -----BEGIN PGP SIGNATURE-----
 >
 > iQMhBAEBCgELBQJS9damBYMB4TOAVhSAAAAAACUAKGlzaXMrc2lnbnN1YmtleUBw
 > YXR0ZXJuc2ludGhldm9pZC5uZXRDRDY2NkI2MTIwOTZFQjM5OUZGMzQ3RURFOUYy
 > NjY5RTREQjZEMDUySxSAAAAAABoAKGlzaXNAcGF0dGVybnNpbnRoZXZvaWQubmV0
 > MzE4QTgzQTk3NUM5MUJENDUzOEMzMTdDNEE3OTIzNTRGQTA3OTcxNi4aaHR0cHM6
 > Ly9ibG9nLnBhdHRlcm5zaW50aGV2b2lkLm5ldC9wb2xpY3kudHh0LJhodHRwczov
 > L2Jsb2cucGF0dGVybnNpbnRoZXZvaWQubmV0L2lzaXMudHh0AAoJEOnyZp5NttBS
 > CXcP/1DFrDbrkUqDk+fgJPiXcLGdOGUA1NlJ6PWZwCUi9dHl6e4lD0c9G2o8U/LX
 > L39/UIebh/ywr+xOu5dZ6SE7aIG36qrhVvyTPqWa8JT8epbAsK5PmyXAGN6/vjnZ
 > +CW0jFKmXPICdRAb3G5mBLlt7hzwpMoNYtuWsZT7B6Wz20fJoHDp5eRJKTxGoWKr
 > knVUMq0qURzB9SwGGJijM8OcosPVrNuNFQCcaEbgPxm1wd2gf+moHbSelQu2T+bs
 > LqPhbs5rzCIDxtW+foHxi7ieOBXozlQF605dgt+We7yRl2ttomZmaf0G1S/kYBMg
 > botAXiS+DjIiUd821qWUUZKRtTOMS3w6robtp+PIdQ+IFTg2yv51K3EEBFf4sSY7
 > alXbG+uJlPV+eIY2SdOdXwFbzfh3PbEw1XDE0Xj6PHkcPLqsHVEejrF3Ga3mjyM4
 > IV4Sj9jSySMnBg6qQiLxEdB0J1wjU0bKL5d8iJK0/CiinshPwcdKACp+urPS+EoB
 > U6sRrBmEEHF8Msmga/WbHEoVU2L8fSohseo9XO2VHom0ZNpdvY42QygixjA0xOR2
 > pf9w1Rvfd0ocMwRxRsJZ8Oh8P1B9LhxwFz96SvBxv7hsYmmX4QkektAYKQMOfCYK
 > dQ6egFqnK1D9vromVCFjzA5nMMAZwAlnJUxHa7ZMnMr+CpNV
 > =8j/+
 > -----END PGP SIGNATURE-----
 >
 > Feb 08 07:03:02 [INFO] Sending reply to 'isis@xxxxxxxxx'
 > }}}
 >
 >
 [[Image(https://trac.torproject.org/projects/tor/attachment/ticket/9264/9264-sysrqb_rebased_0-BridgeDB%20%C2%B7%202014-02-08%2007-05-19.png)]]

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9264#comment:27>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs