mirrors/arti.git/crates/arti-client, branch arti-v1.1.7 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.7 2023-08-01T14:57:55Z Increment patchlevel versions of crates with minor changes 2023-08-01T14:57:55Z Nick Mathewson nickm@torproject.org 2023-08-01T14:57:55Z urn:sha1:3acdf102c705314aec63679e97240bb7d981d1c8 These crates are at version 0.x.y, so we don't need to distinguish new-feature changes from other changes: ``` tor-basic-utils fs-mistrust tor-error tor-geoip tor-checkable tor-linkspec tor-netdoc tor-netdir tor-persist tor-ptmgr tor-hsservice ``` This crate has a breaking change, but only when the semver-breaking feature `experimental-api` is enabled: ``` tor-config ``` This crate is at version 1.x.y, but has no new public APIs, and therefore does not need a minor version bump: ``` arti ``` Update minor versions on crates that have had breaking changes 2023-08-01T14:51:25Z Nick Mathewson nickm@torproject.org 2023-08-01T14:51:25Z urn:sha1:6f2ae5960393b64c1d7615d2d523e050d3bebe5a These crates had first-order breaking changes: ``` retry-error tor-keymgr tor-proto tor-hsclient tor-rtmock ``` Additionally, these broke because they re-exposed RetryError: ``` tor-circmgr ``` Additionally, these broke because they may re-expose something from tor-proto: ``` arti-client tor-chanmgr tor-dirclient tor-dirmgr tor-guardmgr ``` Additionally, these broke for other fiddly reasons: `tor-ptmgr` implements traits from tor-chanmgr, which has a breaking change above. `arti-hyper` exposes types from arti-client in its API. pass reconfigure_lock guard into TorClient::reconfigure_inner 2023-07-25T17:31:36Z sw1tch sw1tchwitch@protonmail.com 2023-07-25T17:31:36Z urn:sha1:b6873a9b84de614f3efa67d6f4fffd7b9ca68daa cargo fmt 2023-07-24T12:48:19Z sw1tch sw1tchwitch@protonmail.com 2023-07-24T12:48:19Z urn:sha1:7347d45accbf68db0699386faf12ca024233a49f fixes deadlock in TorClient::reconfigure 2023-07-24T11:39:49Z sw1tch sw1tchwitch@protonmail.com 2023-07-23T10:15:32Z urn:sha1:3eee40898556b4d3c55ea71c904d288df1d50e93 Revert "keymgr: Require callers to be explicit about which keystore to get keys from." 2023-07-21T11:21:36Z Gabriela Moldovan gabi@torproject.org 2023-07-21T10:55:46Z urn:sha1:98337afec991077c861c672d9dbd6e95efc0c9a2 This reverts commit 38a6c74c7894dc96b16c9039cacc2a4023977b05. This also updates some tests to make them compile with the reverted version of the code. keymgr: Require callers to be explicit about which keystore to get keys from. 2023-07-20T18:24:57Z Gabriela Moldovan gabi@torproject.org 2023-07-19T13:24:08Z urn:sha1:38a6c74c7894dc96b16c9039cacc2a4023977b05 keymgr: Explicitly specify the default keystore for `KeyMgr`. 2023-07-20T18:23:58Z Gabriela Moldovan gabi@torproject.org 2023-07-18T18:10:52Z urn:sha1:9f5974fb7f1ace232ff75524344df68f2ac4355a keymgr-config: Make fields private, add function for checking if keystore is enabled. 2023-07-20T18:23:48Z Gabriela Moldovan gabi@torproject.org 2023-07-18T14:08:30Z urn:sha1:ac93b1aef65671c1003edc695cad9e4137946129 Hiding the underlying value of `enabled` enables us to give it a different `auto` value depending on whether the `keymgr` feature is enabled or not (it defaults to `true` if `keymgr` is enabled, and `false` otherwise). arti-client: Use a default keystore config if `experimental-api` is disabled. 2023-07-20T18:23:45Z Gabriela Moldovan gabi@torproject.org 2023-07-18T13:06:58Z urn:sha1:f18e773332d19382423b0e79bb2051975c29118d The `experimental-api` was only meant to apply to the use of the unstable `ArtiNativeKeystoreConfig` in the Arti config. `experimental-api` was _not_ supposed to be used for enabling/disabling the keystore (that's what the `enabled` flag is for).