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

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



Yawning Angel transcribed 2.7K bytes:
> On Thu, 10 Sep 2015 07:01:58 +0000
> isis <isis@xxxxxxxxxxxxxx> 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).
> 
> Regards,
> 
> -- 
> Yawning Angel

Sounds like something we could work on at the dev meeting? :)

-- 
 ââ isis agora lovecruft
_________________________________________________________
OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35
Current Keys: https://blog.patternsinthevoid.net/isis.txt

Attachment: signature.asc
Description: Digital signature

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