mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.0 2022-11-24T17:17:36Z 2022-11-24T17:17:36Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-11-23T17:04:38Z urn:sha1:1a39a0c7e90204d6352fcc59811a355ae22aa43a Enums with variants conditional on cargo features must be non-exhaustive, because cargo features are supposed to be additive, meaning that enabling a feature (which might happen due to some random distant thing) ought not to break things using that enum. There were surprisingly few places to fix this. 2022-11-21T14:54:39Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-11-17T18:38:12Z urn:sha1:fec66077de9f3a2a10d7db2e589c2c5981a9f859 And the error too. We need this for the API for BridgeConfigBuilder, where the user can specify any kind of target "address", even a hostname. It's already non-conditional, it's just that the name is too limiting. In this commit: * Change in tor-linkspec * Export transitional aliases * Add TODOs to remove the transitional aliases 2022-11-21T14:54:39Z Ian Jackson ijackson@chiark.greenend.org.uk 2022-11-17T14:28:10Z urn:sha1:224f4905e4af60af313fb258bc23a08a2b601993 2022-11-17T14:12:57Z Nick Mathewson nickm@torproject.org 2022-11-17T14:12:57Z urn:sha1:95081198e5f7a8d707dfbf7a1c2be493072d0192 Nothing used this; if anything wants it, it would be better off calling `.display_chan_target()`. 2022-10-24T12:59:12Z Nick Mathewson nickm@torproject.org 2022-10-20T14:46:00Z urn:sha1:bb117a4bd4ed264011619101881950371145e050 Now it contains either an `OwnedChanTarget` or an `OwnedCircTarget`, which will let `GuardMgr` return bridges that can be used to make circuits. As part of this change, it was necessary to revise some address-modification functions that applied to filters and `OwnedChanTarget`. Now they do the smart thing, and remove only the address that are in the `ChanMethod`. This means that the addresses from HasAddrs are still accurate about which addresses the relay "has". 2022-10-21T13:21:43Z Nick Mathewson nickm@torproject.org 2022-10-20T13:49:00Z urn:sha1:00f887db703b04fbe911d29bb91767a101062ef4 2022-10-15T13:57:45Z Nick Mathewson nickm@torproject.org 2022-10-15T13:57:45Z urn:sha1:ddc5b63a19766c2900f72408ad052352aba14821 2022-10-06T19:13:05Z Nick Mathewson nickm@torproject.org 2022-10-05T15:25:19Z urn:sha1:ce09b7c96f445def056a5718024e30d663195ac1 HasAddr used to mean "Here are addresses that I have, at which I can be contacted." But "Where (and how) can I be contacted?" is now a question for HasChannelMethod to answer. (We still need to have "HasAddr", though, so we can answer things like "what country is this relay in" and "are these relays in the same /8?") So this commit introduces: * A new trait for adding an implementation of HasChannelMethod in terms of HasAddr. * A requirement on ChanTarget that it needs to implement HasChannelMethod. There is some temporary breakage here, marked with "TODO pt-client", that I'll fix later in this branch. 2022-10-04T20:05:40Z Nick Mathewson nickm@torproject.org 2022-10-04T15:48:31Z urn:sha1:11caa46525e23024d9f0a30eb2adf84e266a882b This is based on the type generated with n_key_set, with a couple of extra methods to take advantage of RelayId and RelayIdRef. 2022-10-03T18:16:56Z Nick Mathewson nickm@torproject.org 2022-10-03T15:26:11Z urn:sha1:88a06225b9e294afddb1985648fdf4b7ff470c72