mirrors/arti.git/crates/tor-hsservice/Cargo.toml, branch arti-v1.1.12mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.122024-01-09T13:17:45ZFollowup minor version bumps.2024-01-09T13:17:45ZNick Mathewsonnickm@torproject.org2024-01-09T13:17:45Zurn:sha1:8e883e2b00d717985746c2402bc6ee394cfd3fdf
These crates had no changes previously, but they depend on crates
that had breaking changes themselves.
tor-linkspec
tor-hspow
Patchlevel version bumps in preparation for 1.1.12.2024-01-09T13:11:17ZNick Mathewsonnickm@torproject.org2024-01-09T13:07:43Zurn:sha1:ef150707800e7aba78948f0b5dc5a2dcefaf62b6
This crate doesn't have a meaningful public API, so it just gets a patchlevel bump:
arti
These crates had nonbreaking changes, and get a patchlevel bump:
tor-rtcompat
fs-mistrust
tor-llcrypto
tor-cert
Breaking version bumps in preparation for 1.1.12.2024-01-09T13:07:43ZNick Mathewsonnickm@torproject.org2024-01-09T13:07:43Zurn:sha1:565b44dc8e0a40d82b2eb32869b04b807b19cd9c
These crates have breaking changes on their own:
tor-error
tor-netdoc
tor-dirmgr
tor-keymgr
Because of the breaking change in tor-error, and the fact that
basically every crate publicly depends on tor-error (by implementing
ErrorKind), we need to call this a breaking change on all of the
following:
tor-config
tor-geoip
tor-rtmock
tor-log-ratelim
tor-rpcbase
tor-bytes
tor-hscrypto
tor-socksproto
tor-cell
tor-proto
tor-netdoc
tor-netdir
tor-persist
tor-chanmgr
tor-ptmgr
tor-guardmgr
tor-circmgr
tor-dirclient
tor-dirmgr
tor-keymgr
tor-hsclient
tor-hsservice
tor-hsrproxy
arti-client
arti-rpcserver
arti-config
arti-hyper
arti-testing
Run "fixup-features" in preparation for release.2024-01-08T18:30:34ZNick Mathewsonnickm@torproject.org2024-01-08T18:30:34Zurn:sha1:41782552e9602390cd6fbf79374dd4e2218ea119Update to derive-adhoc 0.82024-01-02T16:17:19ZIan Jacksonijackson@chiark.greenend.org.uk2024-01-02T15:58:05Zurn:sha1:2add0c7c26b576285d871d01e031f58f94039f14
As recommended in the d-a changelog, I'm not calling this a breaking
change to our APIs.
tor-hsservice: Cargo.toml: sort2023-12-13T17:03:23ZIan Jacksonijackson@chiark.greenend.org.uk2023-12-12T18:47:36Zurn:sha1:49e9b8a1b9f97feb2532d259ecbe367c5b5c5b5etor-hsservice: Plumb state dir and its mistrust into ipt_mgr2023-12-13T17:03:23ZIan Jacksonijackson@chiark.greenend.org.uk2023-12-12T15:29:49Zurn:sha1:a917c6c902e0fcb8485cd9f6184f34ba0d7f9c12
This is needed for the replay logs.
It's a shame that CheckedDir is (i) a bit unergonomic (ii) has an
extra bool in it, or we could pass one of those instead of these two
arguments.
Since HS's might be created after startup, TorClient must have these
fields.
tor-hsservice tests: replay: Provide for a filesystem lockfile2023-12-13T17:03:23ZIan Jacksonijackson@chiark.greenend.org.uk2023-12-04T13:28:41Zurn:sha1:722bb3ae4d952d98b87f93dd7b84fed9b6df7651
This is to prevent current use of the same directory of replay logs by
different instances.
tor-hsservice: Test the TryFrom<&KeyPath> KeySpecifier impl.2023-12-05T16:37:43ZGabriela Moldovangabi@torproject.org2023-11-30T14:01:41Zurn:sha1:0aca5eb5f808466f339335d67cc09ab785159469tor-hsservice: Define key specifiers for IPT keys2023-12-04T18:58:10ZIan Jacksonijackson@chiark.greenend.org.uk2023-11-23T11:15:29Zurn:sha1:113d56f168198ce8a1464596872cf0376e59e3f2