mirrors/arti.git/crates/tor-error, branch arti-v1.1.6 mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.6 2023-06-30T12:42:21Z Bump patchlevel versions on crates with smaller changes 2023-06-30T12:42:21Z Nick Mathewson nickm@torproject.org 2023-06-30T12:42:21Z urn:sha1:de13a7319b7de5a336a70f128d1904954ed77f82 Done with the commands below. The following crates have had various changes, and should get a patchlevel bump. Since they are pre-1.0, we do not need to distinguish new APIs from other changes. ``` cargo set-version --bump patch -p arti-client cargo set-version --bump patch -p safelog cargo set-version --bump patch -p tor-bytes cargo set-version --bump patch -p tor-cert cargo set-version --bump patch -p tor-circmgr cargo set-version --bump patch -p tor-config cargo set-version --bump patch -p tor-consdiff cargo set-version --bump patch -p tor-dirclient cargo set-version --bump patch -p tor-dirmgr cargo set-version --bump patch -p tor-error cargo set-version --bump patch -p tor-hsservice cargo set-version --bump patch -p tor-linkspec cargo set-version --bump patch -p tor-llcrypto cargo set-version --bump patch -p tor-netdir cargo set-version --bump patch -p tor-netdoc cargo set-version --bump patch -p tor-proto cargo set-version --bump patch -p tor-rpcbase cargo set-version --bump patch -p tor-socksproto ``` This crate has new features, but no new non-experimental Rust APIs. So even though it is post-1.0, it gets a patchlevel bump. ``` cargo set-version --bump patch -p arti ``` tor-error: Make KeystoreFsPermissions experimental for now 2023-06-29T18:51:04Z Ian Jackson ijackson@chiark.greenend.org.uk 2023-06-29T18:17:52Z urn:sha1:69129bf2b4af9fdcd93a9a0d07d5e548733f708e Let's defer this decision. tor-error: Add KeystoreAccessFailed, KeystoreFsPermissions to ErrorKind. 2023-06-28T10:59:00Z Gabriela Moldovan gabi@torproject.org 2023-06-27T10:37:02Z urn:sha1:6ed8f5b9ea70d9ede112e3308a56dad6725d7bb5 tor-error: Add KeystoreCorrupted to ErrorKind. 2023-06-28T10:59:00Z Gabriela Moldovan gabi@torproject.org 2023-06-27T10:25:23Z urn:sha1:c8a128cc598273165384b726a920a37ad5e397e6 tor-error: Mark define_asref_dyn_std_error as non-experimental 2023-06-23T16:49:46Z Nick Mathewson nickm@torproject.org 2023-06-22T19:40:56Z urn:sha1:085c45ed1871bea7661480292a6cad0273803fae (I see no problems with this macro. In the worst case, we deprecate it someday.) tor-error: Stabilize OnionService error kinds 2023-06-22T17:17:08Z Nick Mathewson nickm@torproject.org 2023-06-22T17:17:08Z urn:sha1:3ccec0b04ae97f8f491343c9807b5690d679a477 tor-error: typo fix in a comment. 2023-06-22T17:15:50Z Nick Mathewson nickm@torproject.org 2023-06-22T17:15:50Z urn:sha1:3d4181bcd448f665585a4ad2f94db9d5b8d9f68d Remove onion service descriptor-related errorkinds. 2023-06-22T17:11:06Z Nick Mathewson nickm@torproject.org 2023-06-22T17:11:06Z urn:sha1:33bfa7c7a86035342b09920cbf4c85e83889bb46 These have been subsumed by other errorkinds, mostly OnionServiceProtocolViolation and TorProtocolViolation. In particular please review the change in tor-hsclient closely; I am not sure about the new errorkinds for the error there. Merge branch 'socks_errorkinds' into 'main' 2023-06-22T16:15:55Z Nick Mathewson nickm@torproject.org 2023-06-22T16:15:55Z urn:sha1:610ed2d45745fa7fa4d7d0acfe439ec80e97c8d5 Generate correct-ish socks5 errors for onion service errors. Closes #736 See merge request tpo/core/arti!1279 New ErrorKind for invalid onion addresses 2023-06-22T14:57:08Z Nick Mathewson nickm@torproject.org 2023-06-22T14:51:52Z urn:sha1:967cae6cede19e7911ea2bed5f8e6f571c72d0b2 Use this to emit HS_BAD_ADDRESS as appropriate.