Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

Hi, Funny, this is exactly the direction my thinking has been going. There are too many different variations on restrictions - it might make sense to just have a large enough sampled set, and then filter it with the further restrictions. If nothing is found, we can fail closed at least. Cheers --

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

On 04/04/16 11:47, George Kadianakis wrote: > I wonder what would happen there if FascistFirewall gets toggled on and off. > > If our guardlist was sampled when FascistFirewall was on, shouldn't we sample > from the beginning if FascistFirewall goes off? That's terrible though since > we > lose a

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

Tim Wilson-Brown - teor writes: > [ text/plain ] > >> On 27 Mar 2016, at 05:42, s7r wrote: >> >> Hello, >> >> teor, asn, see comments inline. >> >> On 3/24/2016 5:00 PM, Tim Wilson-Brown - teor wrote: >> [snip] >> The proposal ignores client bootstrap. >> >> There are a limited number of har

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

> On 25 Mar 2016, at 22:26, George Kadianakis wrote: > > Tim Wilson-Brown - teor writes: > >> [ text/plain ] >> >>> On 25 Mar 2016, at 00:31, George Kadianakis wrote: >>> >>> Tim Wilson-Brown - teor mailto:teor2...@gmail.com>> >>> writes: >>> [ text/plain ] > On 24 Mar 2016

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

> On 27 Mar 2016, at 05:42, s7r wrote: > > Hello, > > teor, asn, see comments inline. > > On 3/24/2016 5:00 PM, Tim Wilson-Brown - teor wrote: > [snip] The number of directory guards will increase when 0.2.8-stable is released and relays and clients upgrade. In 0.2.8, relays acc

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

Hi, On 3/27/2016 1:00 PM, George Kadianakis wrote: >>[snip] >> >> https://lists.torproject.org/pipermail/tor-dev/2015-November/009871.html >> > > Hmm, this seems like something worth considering. > > IIUC you are basically suggesting using a single guardlist instead of having > two. And then al

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

s7r writes: > [ text/plain ] > Hello, > > teor, asn, see comments inline. > > On 3/24/2016 5:00 PM, Tim Wilson-Brown - teor wrote: > [snip] [snip] >> This isn't how Tor works - it tries multiple guards simultaneously. >> (See below for details.) >> Can we rework this calculation to take

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

Hello, teor, asn, see comments inline. On 3/24/2016 5:00 PM, Tim Wilson-Brown - teor wrote: [snip] >>> The number of directory guards will increase when 0.2.8-stable is >>> released and relays and clients upgrade. >>> In 0.2.8, relays accept tunnelled directory connections even if they >>> do not

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

Tim Wilson-Brown - teor writes: > [ text/plain ] > >> On 25 Mar 2016, at 00:31, George Kadianakis wrote: >> >> Tim Wilson-Brown - teor mailto:teor2...@gmail.com>> >> writes: >> >>> [ text/plain ] >>> On 24 Mar 2016, at 22:55, George Kadianakis >>> > wrote: >

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

> On 25 Mar 2016, at 00:31, George Kadianakis wrote: > > Tim Wilson-Brown - teor mailto:teor2...@gmail.com>> > writes: > >> [ text/plain ] >> >>> On 24 Mar 2016, at 22:55, George Kadianakis >> > wrote: >>> >>> - How exactly should directory guards work? Should th

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

Tim Wilson-Brown - teor writes: > [ text/plain ] > >> On 24 Mar 2016, at 22:55, George Kadianakis wrote: >> >> - How exactly should directory guards work? Should the guard lists be >> initialized only with directory guards? Or should we just initialize our >> guard lists from the set of all g

Re: [tor-dev] Proposal 259: New Guard Selection Behaviour

> On 24 Mar 2016, at 22:55, George Kadianakis wrote: > > - How exactly should directory guards work? Should the guard lists be > initialized only with directory guards? Or should we just initialize our > guard lists from the set of all guards, and just skip non-V2Dir guards > whenever we need

[tor-dev] Proposal 259: New Guard Selection Behaviour

Hello, proposal 259 has evolved plenty since the last time it was posted on [tor-dev]. All the technical discussion can be found in various threads, and here is a thread about the proposal itself as it is now. The current proposal is pretty much done, and it's currently being implemented for test