mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.5 2023-02-28T11:10:17Z 2023-02-28T11:10:17Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-02-24T14:26:25Z urn:sha1:f63c7c48afd94fe9d09746f0b76fbaff8d4a1a79 Fixes #756 2023-01-28T17:43:08Z Nick Mathewson nickm@torproject.org 2023-01-24T15:46:56Z urn:sha1:5236c5cf887af0bd321ca80fb6dba991289549d6 This logic is a bit tricky, so I've tried to document it and add fairly good tests. The silver lining is that the external API for all of this logic will make it invisible and hidden. There are some cases where I added functions that I think might eventually get lowered into MdConsensus: But I don't want to lower too much right now, since the convention for our netdoc accessors is that they are fairly unsophisticated, and they show you the document as it is. Closes #686 2023-01-11T14:04:13Z Nick Mathewson nickm@torproject.org 2023-01-10T14:23:42Z urn:sha1:5b74ef7af9be657918b1b2c8672f35b269c23198 * It is the NetDir's responsibility to tell the caller what the time period is. * There can be up to two secondary time periods. * Each time period has a single SRV. * Secondary time periods only apply for onion services, when they publish. * When publishing, the correct input is a time period. 2022-07-26T09:40:53Z Nick Mathewson nickm@torproject.org 2022-07-25T14:55:23Z urn:sha1:c39aa5de73fb8f1747752b7b722e8b94b01e315b Over the years we've found that most callers who want a netdir want what C Tor calls a "reasonably live" network directory: One that is not expired by too much, or too far in the future. But a few want a _strictly_ live directory: one that says it is valid now, with no tolerances. And a few want _any_ directory, no matter how expired it is. This commit adds net methods to NetDirProvider to provide these directories. I think that most use cases will want to explicitly think about what kind of directory they want, so I've made `netdir` the simplest method. I might remove `timely_netdir` by the end of this branch; see TODO comments. Part of #518. 2022-02-15T19:43:36Z Nick Mathewson nickm@torproject.org 2022-02-15T19:43:36Z urn:sha1:058e4d7705c09b9e5a9d45e10b84a409308235b2 There's no reason to have the test-network-construction code share an error enum with the main netdir code. 2022-02-15T19:36:15Z Nick Mathewson nickm@torproject.org 2022-02-15T19:36:15Z urn:sha1:ceb8e8c1e2864fbd326cf59c814209cf67e10a07 This turns out to have been most of them, which simplifies matters a lot. 2022-02-14T15:46:04Z Nick Mathewson nickm@torproject.org 2022-02-14T15:46:04Z urn:sha1:b27c51d3a2ad4a7b8ec00c2a06be55af9459507a Every other case of tor_netdoc::Error means a parse failure. This one, though, means a failure to construct a document. 2021-08-27T13:53:09Z Nick Mathewson nickm@torproject.org 2021-08-27T13:53:09Z urn:sha1:557a0ff40b3731d4690767de27010bbeff08777d This will cause some pain for now, but now is really the best time to do this kind of thing.