mirrors/arti.git/crates/tor-netdir/src/details.rs, branch main mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=main 2026-06-24T09:01:03Z tor-netdoc: Wrap port policies in Intern 2026-06-24T09:01:03Z Clara Engler cve@cve.cx 2026-06-18T14:46:36Z urn:sha1:7ad86bce0d99a28519684d1cdb88ff6ec3adcf62 This commit wraps the port policies in an Intern. Merge branch 'flags-url' into 'main' 2026-03-12T09:45:55Z Clara Engler cve@cve.cx 2026-03-12T09:45:55Z urn:sha1:e54c4d396ef8de6f6523d1c5cf7f91439aa468a0 tor-netdir: Add spec link to flag descriptions See merge request tpo/core/arti!3768 tor-netdir: Add spec link to flag descriptions 2026-03-11T15:27:13Z Ian Jackson ijackson@chiark.greenend.org.uk 2026-03-11T15:27:13Z urn:sha1:1bfc7b24141f4b8a7cb240c8518818feb5a2020c tor-netdir: Simply exit documentation 2026-03-09T07:45:49Z Clara Engler cve@cve.cx 2026-03-09T07:45:49Z urn:sha1:4abfc238dd6088398758fb97771f49dffd0b3c5e No need to over-engineer this, let's keep it simple. tor-netdir: Add is_flagged_exit() to RelayDetails 2026-03-05T08:50:43Z Clara Engler cve@cve.cx 2026-03-05T08:50:43Z urn:sha1:e96382b6ce2a208aca334947424c3900750f68ae This commit adds a method called `is_flagged_exit` to `RelayDetails` in order to check whether the node is considered to be usable as an exit or not. In the Tor VPN app, we need this feature for generating a list of exit relays (per country). Right now, we do this in an incorrect way by only checking on whether port 443 is in the exit policy, which is not a sufficient criteria. tor-netdoc: Combine ConsensusRouterStatus and GenericRouterStatus 2025-08-26T09:41:21Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-08-21T09:34:51Z urn:sha1:7bde61567649ea93e03a7ad63e94a949319c9f03 Now we only need one type. netdir, relay-selection: require Fast and Stable for rendpoints. 2025-05-20T19:22:08Z Nick Mathewson nickm@torproject.org 2025-05-20T13:07:29Z urn:sha1:c51745d1d0cdfb3363d8b505c7c749f70276ab57 Since we don't know what kind of traffic we'll use a rendezvous point for, we don't want to use it if it isn't "Fast" (reasonably high bw) and "Stable" (unlikely to crash soon). hs: Prevent a client from using a `MiddleOnly` relay for onion services 2025-05-20T19:22:08Z Neel Chauhan neel@neelc.org 2025-04-03T00:38:04Z urn:sha1:94baab29f330fd17269e6b44958896b3f9ca794a > The actual impact of this patch is to prevent usage of MiddleOnly > relays as Introduction Points. The Rendezvous Point logic isn't > hooked up yet - nick Use named subprotocol versions throughout arti. 2025-03-12T14:47:05Z Nick Mathewson nickm@torproject.org 2025-03-12T14:47:05Z urn:sha1:90b09cd03ca50ba2aced0f89b5adc5c59d582808 netdir: Consider RelayFamilyIds based on family rules 2025-02-25T14:29:50Z Nick Mathewson nickm@torproject.org 2025-02-10T21:10:15Z urn:sha1:9650d0b75d6a5ce5c554cb0ac04077374a889538 This implements the client side of proposal 321. It's a breaking change in netdir, since in_same_family now takes an extra argument.