Re: [tor-dev] Hashring understanding

Ola Bini writes: > Hi, > > Sorry for the string of emails! > > Hopefully a simple question: > The current proposal contains logic for keeping track of network > up/down and setting timeouts for exponential backoff to test the > network again. But if I understand

Re: [tor-dev] Hashring understanding

Spencer writes: > Hi, > >> >> George Kadianakis: >> Indeed. [The randomly selected guards] > are saved in the state file. Check: >> https://lists.torproject.org/pipermail/tor-dev/2016-February/010355.html >> also see here for another explanation of >> how parts of

Re: [tor-dev] Guards selection - current algorithm simulation

Iván Pazmiño writes: > Hey guys, > > Just wondering if by any chance you have a simulator for the current > algorithm to select guards. It would be very useful to compare against > new algorithm's numbers. > > Thanks, Hello, We don't actually and it's a pity because

Re: [tor-dev] Hashring understanding

Ola Bini writes: > Hi, > > Sorry for this - had some questions about the hashring component of > #259 that I haven't been able to figure out myself. I'm sure it's just > me being unused to the Tor code base and how you write your proposals, > but it would be super helpful

[tor-dev] (no subject)

Hello, a while ago I set up a BSD buildbot for tor[1]. It's actually not just for BSDs, but also for other systems, such as Solaris. I wanted to make it easier to notice when something breaks on non-popular systems, not actively used by the developers. There also is reporting through an IRC bot

[tor-dev] BSD Buildbot on #tor-bots (was: (no subject))

On 02/04/2016 10:07 AM, Christian Sturm wrote: > Hello, > > a while ago I set up a BSD buildbot for tor[1]. It's actually not just > for BSDs, but also for other systems, such as Solaris. I wanted to make > it easier to notice when something breaks on non-popular systems, not > actively used by

Re: [tor-dev] Hashring understanding

Ola Bini writes: > Hi, > >> I think it's fine to use randomness to generate it for now; that's what tor >> also currently does [0]. > Cool - we have a local clone of the specs and updating it with this > understanding. > Great! For better or worse I think making design

Re: [tor-dev] Hashring understanding

Ola Bini writes: > Hi, > > Thanks for the confirmation of our understanding! Very helpful. > > If I understand things correctly, we are supposed to take > GUARDLIST_FAILOVER_THRESHOLD guards from the list of all guards and > generate the GUARDLIST from that. Is that

[tor-dev] Hashring understanding

Hi, > > George Kadianakis: > Indeed. [The randomly selected guards] > are saved in the state file. Check: > https://lists.torproject.org/pipermail/tor-dev/2016-February/010355.html > also see here for another explanation of > how parts of it work: >