[tor-dev] Bridge Guards (prop#188) & Bridge ORPort Reachability Tests

Yawning Angel yawning at schwanenlied.me
Thu Sep 10 09:13:12 UTC 2015

On Thu, 10 Sep 2015 07:01:58 +0000
isis <isis at torproject.org> wrote:
>  3. Should we change how the BridgeAuthority tests Bridge ORPort
> reachability? If so, how?
>  4. If I'm going to refactor all of this, are there other (future)
> things I should take into account?
>     For example, if self-testing is disabled for Bridges, and, due to
> #7349, [2] the BridgeAuthority isn't testing reachability either,
> then how will the BridgeAuthority know if (any of) the Bridge's PTs
> are reachable? (One solution might be to, in that case, have the
> BridgeAuthority lie and tell BridgeDB that such Bridges were
> reachable, letting BridgeDB do the PT reachability testing.)

All of this seems to me like we need to sit down somewhere (in
meatspace or online), map out how the current system of:

 * Clients
 * Bridges
 * Bridge Guards
 * The Bridge Authority

fits together, and figure out how it can be redesigned in a way that is
more inline with how things work now/need to work now (PTs were not a
thing when this started being one of the bigger stumbling blocks).


Yawning Angel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150910/46561e2c/attachment.sig>

More information about the tor-dev mailing list