mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=tor-llcrypto-v0.4.4 2023-03-06T13:45:05Z 2023-03-06T13:45:05Z Nick Mathewson nickm@torproject.org 2023-03-06T13:45:05Z urn:sha1:7129807843a8b71a5ef106f3ca65a63244faaf8d 2023-02-28T15:06:41Z Nick Mathewson nickm@torproject.org 2023-02-28T15:06:41Z urn:sha1:886faa96b3c0e42ba066ddc5de73209b10ce58da 2023-02-17T20:26:23Z Nick Mathewson nickm@torproject.org 2023-02-17T20:26:23Z urn:sha1:bc68974212654ed9d1ff530aba071d241d047de4 Unlike linkspec, this doesn't validate the actual contents of the specifiers. We'll use this so we can handle the linkspec list for an introduction point in an HsDesc, and just pass it on when constructing our circuits. I haven't added any accessor or constructor functions, because I don't expect to need them. 2022-11-30T22:10:29Z Nick Mathewson nickm@torproject.org 2022-11-30T22:10:29Z urn:sha1:e0aeda3071ec89c0e7b8b53036c576c1242e3e1f 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