mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.2.0 2022-03-30T14:41:40Z 2022-03-30T14:41:40Z Nick Mathewson nickm@torproject.org 2022-03-29T15:17:34Z urn:sha1:3e92d30e4999f0cd50afd3359c73abfdbaf61d8a 2022-03-30T14:41:39Z Nick Mathewson nickm@torproject.org 2022-03-29T14:55:20Z urn:sha1:6282df34fb00c3b8b686553e05f8d3172b017ed0 The FirstHopId type now records an enum that stores whether the hop is a guard or a fallback. This change addresses concerns about remembering to check the type or source of an Id before passing it down to the FallbackState or GuardSet. Making this change required an API change, so that dirmgr can report success/failure status without actually knowing whether it's using a fallback or a guard. 2022-03-30T14:40:59Z Nick Mathewson nickm@torproject.org 2022-03-29T13:05:39Z urn:sha1:13af6134f6180f7241daca9206fa49ed5f26829d This is preparation for having separate GuardId and FirstHopId types that distinguish which back-end they index. 2022-03-30T12:55:58Z Nick Mathewson nickm@torproject.org 2022-03-30T12:55:58Z urn:sha1:700e491813f84d76446193aef7121a329b774717 2022-03-30T12:44:25Z eta tor@eta.st 2022-03-30T12:44:25Z urn:sha1:fd081742fa13e8464ad46123d83617165587d4f4 Don't use SystemTime::now() Closes #306 See merge request tpo/core/arti!365 2022-03-21T14:27:53Z Nick Mathewson nickm@torproject.org 2022-03-21T14:24:20Z urn:sha1:8306a9cdcf15ae81d9067282c1aff460f8c767d0 2022-03-21T13:06:32Z Nick Mathewson nickm@torproject.org 2022-03-16T18:07:52Z urn:sha1:eed1f06662366511fe5fd15ac0ab0cb69497f2cf When all guards are down, we would previously mark them all as up, and retry aggressively. But that's far too aggressive: if there's something wrong with our ability to connect to guards, it makes us hammer the network over and over, ignoring all the guard retry timeouts in practice. Instead, * We now allow the `pick_guard()` function to fail without automatically retrying. * We give different errors in the cases when all our guards are down, and when all of the guards selected by our active usage are down. * Our "guards are down" error includes the time at which a guard will next be retriable. This is part of #407. 2022-03-21T13:06:32Z Nick Mathewson nickm@torproject.org 2022-03-16T16:58:35Z urn:sha1:cb103e04cf4d985333a6949f0fd646258dcedcd2 C tor used one schedule, and guard-spec specified another. But in reality we should probably use a randomized schedule to retry guards, for the reasons explained in the documentation for RetrySchedule. I've chosen the minima to be not too far from our previous minima for primary and non-primary guards. This is part of #407. 2022-03-02T18:06:37Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-03-02T17:48:10Z urn:sha1:daa44df22155136d934de860c826068494936072 2022-02-25T23:33:44Z trinity-1686a trinity@deuxfleurs.fr 2022-02-25T23:33:44Z urn:sha1:f06b25601006ba42c427349837dca6d5634bc718