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

Tim Wilson-Brown - teor transcribed 19K bytes: >> On 12 Sep 2015, at 17:26, isis wrote: >>> Tim Wilson-Brown - teor transcribed 23K bytes: On 10 Sep 2015, at 17:01, isis wrote: 2.b. If it is useful to people, then the best way I can

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

> On 12 Sep 2015, at 17:26, isis wrote: > > ... > > However, for "double onion services" — or whatever we're calling the thing > that > is (historical) hidden services 2.0 — your point is a good one; I'm starting > to > realise more and more that defences for "double

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

> On 12 Sep 2015, at 17:26, isis wrote: > > Tim Wilson-Brown - teor transcribed 23K bytes: >> >>> On 10 Sep 2015, at 17:01, isis wrote: >>> 4.4.1. Bridge Reachability Self-Testing Before a Bridge uploads its descriptors to the

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

Tim Wilson-Brown - teor transcribed 23K bytes: > > > On 10 Sep 2015, at 17:01, isis wrote: > > > >> 4.4.1. Bridge Reachability Self-Testing > >> > >> Before a Bridge uploads its descriptors to the BridgeAuthority, it > >> creates a special type of testing circuit which

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

> On 10 Sep 2015, at 17:01, isis wrote: > > Hey all, > > I have a working implementation of proposal #188, [0] which specifies a > mechanism by which tor's (rather accidental) loose-source routing feature is > utilised by Bridges in order to transparently inject a Bridge

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

On Thu, 10 Sep 2015 07:01:58 + isis 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

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

Hey all, I have a working implementation of proposal #188, [0] which specifies a mechanism by which tor's (rather accidental) loose-source routing feature is utilised by Bridges in order to transparently inject a Bridge Guard into all client circuits. (See #7144. [1]) Currently, I am updating

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

On 10 September 2015 at 02:01, isis wrote: > 2.a. First, if there aren't any other reasons for self-testing: Is Bridge > reachability self-testing actually helpful to Bridge operators in > practice? Don't most Bridge operators just try to connect, as a

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 + > isis 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