mirrors/arti.git/crates/tor-hscrypto, 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:11:17ZPatchlevel 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
Merge branch 'wallclock-time' into 'main'2023-12-13T16:09:53Zgabi-250gabi@torproject.org2023-12-13T16:09:53Zurn:sha1:ca90f9cf017e269071b1364587c51a75ad5c5995
tor-hscrypto: Return 0 if the timestamp is before the start of the TP.
Closes #1155
See merge request tpo/core/arti!1828tor-hscrypto: Return 0 if the timestamp is before the start of the TP.2023-12-13T12:09:21ZGabriela Moldovangabi@torproject.org2023-12-13T11:56:30Zurn:sha1:c853c48ea1e143bbdeb77d1b968d6f14aa62f6e1
#1155 was happening because we couldn't compute the offset of the
current time from the start of the _next_ TP
(`TimePeriod::offset_within_period` expected `when` to come after the
start of the TP). `TimePeriod::offset_within_period` now returns an
offset of 0 for timestamps that come before the start of the TP, to
support computing revision counters for the descriptors uploaded to
the HsDirs from the ring associated with the next TP.
Fixes #1155
hscrypto: Remove a "TODO HSS" about a no-longer-unused type.2023-12-12T12:41:01ZNick Mathewsonnickm@torproject.org2023-12-12T12:37:54Zurn:sha1:e279b3d5c70c9912d35156d0f0e996cdf6ff8c8eRemove semver.md files.2023-12-04T17:39:07ZNick Mathewsonnickm@torproject.org2023-12-04T17:39:07Zurn:sha1:0dc447123f2250d5d1fb5af0a268d59d018c9b64Bump minor versions in preparation for release2023-12-04T16:35:23ZNick Mathewsonnickm@torproject.org2023-12-04T16:22:58Zurn:sha1:fba95e4b4708929ed09554632acd2e9f15e3c086
This crate is new, and gets a bump to 0.1.0.
tor-log-ratelim
This crate had a breaking change:
tor-persist
tor-llcrypto had a breaking change. These crates _are_
tor-llcrypto, or (transitively) depend on it. I am assuming that
they all re-expose something from it in a way that matters:
tor-llcrypto
tor-bytes
tor-hscrypto
tor-socksproto
tor-checkable
tor-cert
tor-linkspec
tor-cell
tor-proto
tor-netdoc
tor-consdiff
tor-netdir
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-hyper
Bump patchlevel versions in preparation for release2023-12-04T16:33:36ZNick Mathewsonnickm@torproject.org2023-12-04T16:22:58Zurn:sha1:606905bd1fa3307a77a02463fa863f4c2b7cb890
These crates had backward-compatible changes, and get a patchlevel
bump only:
fs-mistrust
tor-error
tor-config
tor-rtcompat
tor-rtmock
This crate exposes no non-CLI APIs, and gets a patchlevel bump only:
arti
Merge branch 'msrv-bump-1.70' into 'main'2023-11-30T14:40:45ZIan Jacksoniwj@torproject.org2023-11-30T14:40:45Zurn:sha1:7b23daffb5c2e903881c9b2d64a0bccc7b3f698e
Increase our MSRV to 1.70
See merge request tpo/core/arti!1773llcrypto: Hide the members of ExpandedKeypair.2023-11-29T17:10:18ZNick Mathewsonnickm@torproject.org2023-11-29T17:10:18Zurn:sha1:adc3209c6bef9cc03542c31c22c0f308938e1643
With this change, we no longer expose the ExpandedSecretKey
unescorted, which makes it harder to misuse the API.