mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.3 2022-01-10T15:10:41Z 2022-01-10T15:10:41Z eta tor@eta.st 2022-01-10T15:10:41Z urn:sha1:de1b19c22a60aa7e86c56023b65b14722ac33c05 That's what I get for blindly trusting @nickm :p 2022-01-10T14:02:24Z eta tor@eta.st 2022-01-10T14:02:24Z urn:sha1:da848a1b9cb4cf6b829f24a4b7b994ba9e60b6ae Fix ticket 178: Don't use a NetDir until we have microdescriptors for all of our primary guards. Closes #178 See merge request tpo/core/arti!220 2022-01-07T18:16:06Z Nick Mathewson nickm@torproject.org 2022-01-07T18:16:06Z urn:sha1:d9b423c17f485126a3dea4de8da5c45cb03037d2 When our current consensus is getting close to being invalid (but it isn't invalid yet), we try to get a new one. So far, so good. But we had a bug: when we went to get a new consensus, we'd see that we had a perfectly fine not-yet-invalid consensus in our cache, reload it, find that it was ready, and continue! This patch fixes our behavior: If we have a usable consensus, then when we reset the bootstrapping process, we ignore any cached consensus. Fixes bug #274. 2022-01-06T20:58:43Z Nick Mathewson nickm@torproject.org 2022-01-06T19:32:54Z urn:sha1:e8e0f673367bb6e1a983e174481c5484e8245c62 This prevents a security-failure condition that could happen if our directory caches don't give us these microdescriptors, but we nevertheless decide that the directory is usable. Closes #178 2021-12-16T14:31:23Z Nick Mathewson nickm@torproject.org 2021-12-16T14:08:15Z urn:sha1:9f6e09b4d1ff7d62cb917d59d36ab946a081d103 Previously we didn't retain the value of our cache_usage field when calling reset() from GetMicrodescsState. This resolves an XXXX comment. 2021-12-16T14:28:51Z eta tor@eta.st 2021-12-16T14:28:51Z urn:sha1:e62212112ca4005fb5c8c3b220716e6f75f4fd5f Refactor directory events to use a new FlagPublisher mechanism. See merge request tpo/core/arti!188 2021-12-16T13:51:34Z Nick Mathewson nickm@torproject.org 2021-12-16T13:51:34Z urn:sha1:b5672cb2c79257cd1ac20de3474ba825cae198b5 This warning occurs if we ask for microdescriptors from our local cache, and our cache gives us something we didn't ask for. It shouldn't be possible, so let's warn when it occurs. This patch resolves an XXXX. 2021-12-14T19:05:02Z Nick Mathewson nickm@torproject.org 2021-12-09T19:10:41Z urn:sha1:7f4578bec162c95da232a2f424abcd5ad55c9496 This approach tries to preserve the current interface, but uses a counter-based event backend to implement a coalescing stream of events that can be represented as small integers. The advantage here is that publishing events no longer needs to be a blocking operation, since there is no queue to fill up. 2021-12-08T00:26:01Z Nick Mathewson nickm@torproject.org 2021-12-08T00:22:54Z urn:sha1:42ae8c7a2ad776cfdc54c9587a3381a8a3189740 This is still not as soon as I'd like: a real change here will require refactoring DirMgr::notify(). 2021-12-07T22:36:16Z Nick Mathewson nickm@torproject.org 2021-12-07T22:36:16Z urn:sha1:e8ca0d7742e984381be130c01bf3ca0a4d20dd91 We can't change the authorities while in-flight: that would be pretty miserable to implement. Similarly we can't change the cache while in-flight. Everything else should be fair game, though there are a couple of tricky bits. I've tried to document those.