Skip to main content
12 events
when toggle format what by license comment
Mar 14, 2017 at 11:29 comment added NewUser Thank you. In any case, I have opened a specific thread about this "problem". The link is: tor.stackexchange.com/questions/14312/…
Mar 14, 2017 at 1:29 comment added cacahuatl The documentation is probably, like the manual, out of date. I can't reproduce the only 1 guard in state file thing you're seeing.
Mar 13, 2017 at 22:06 comment added NewUser So, why does Tor Browser sometimes assign me only one entry guard and sometimes it assign me three entry guard, especially if in its current stable source code (0.2.9.10) an entry guard is set by default? And why the 0.2.9.10 source code establish by default an entry guard, but the directory protocol, version 3, establish by default three entry guards (gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1837)?
Mar 13, 2017 at 22:05 comment added NewUser I'm going to attach screenshots to explain better what I mean. In the first screenshot (available here imgur.com/a/wDtf5) you can see how Tor Browser assigned me one entry guard ONLY. Then, I've deleted the content of the "state" file and I've started Tor Browser again. So, Tor Browser has assigned me three entry guards, as you can see in this screenshot: imgur.com/a/qrUEb. Then, I've re-deleted the content of the "state" file and I've re-started Tor Browser and ¡surprise! Tor Browser has assigned ONLY an entry guard, as you can see in this screenshot: imgur.com/a/pDVts
Mar 13, 2017 at 0:13 comment added NewUser And canonizing ironize, do you know why sometimes my Tor Browser picks three entry guards, but sometimes my Tor Browser picks only an entry guard? (according to I can see in the state file). Additionaly, why the 0.2.9.10 source code establish by default an entry guard, but the directory protocol, version 3, establish by default three entry guards?
Mar 12, 2017 at 22:23 comment added cacahuatl 0.3.x has the new prop-271 guard selection algorithm, which obsoletes most of the work done for prop-236, so your question is about 0.2.9.10 which is where I've cited code for, but 0.3.x will change it entirely (for the better).
Mar 12, 2017 at 18:59 comment added NewUser Wow! Right now I have re-deleted the contents of the "state" file, I have started Tor and I see that the file only shows an 'entry guard'. This time Tor has only selected one and not three as before. Why?
Mar 12, 2017 at 18:11 comment added NewUser 2/2 it is said: * How many guards do we try to keep on our primary guard list? and then, the code sais: return networkstatus_get_param(NULL, "guard-n-primary-guards", DFLT_N_PRIMARY_GUARDS, 1, INT32_MAX); I'm doing a university research about Tor, and in the section about "entry guards" I do not exactly what to say, because the source code establish only 1 entry guard, and the consensus parameters also establish 1 entry guard, but then my Tor Browsers picks 3 entry guards. So, if I say that "Tor picks 3 potential entry guards, but then the client uses only 1 entry guards", would it be right?
Mar 12, 2017 at 18:10 comment added NewUser 1/2 I have been doing some tests with my Tor Browser and I have seen some interesting thing: by default, my Tor Browser ALWAYS picks 3 entry guards (except, evidently, if I use the option "NumEntryGuards NUM" and I specify a concrete number of nodes). I have deleted the content of the file "state" several times and after iniciating Tor Browser, always 3 entry guards appears in that file. In the Tor directory protocol, version 3 it is said (line #1837) this: NumEntryGuards: | Min: 1. Max: 10. Default: 3 |. Additionaly, there's a new entrynodes.c file (release 0.3.0) and in the line #430
Mar 12, 2017 at 14:53 history edited cacahuatl CC BY-SA 3.0
added 522 characters in body
Mar 10, 2017 at 11:50 vote accept NewUser
Mar 9, 2017 at 11:41 history answered cacahuatl CC BY-SA 3.0