mirrors/arti.git/crates/tor-hscrypto/src/time.rs, branch arti-v1.4.5mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.52025-05-27T18:05:01Ztor-hsservice: Make PowManager persist state.2025-05-27T18:05:01ZWesley Aptekar-Casselsme@wesleyac.com2025-02-18T17:36:12Zurn:sha1:0c0ad4f4711971a902418c76e2e0da67c51c370btor-hsservice: Initial parts of PowManager.2025-05-27T17:51:27ZWesley Aptekar-Casselsme@wesleyac.com2025-01-08T18:07:33Zurn:sha1:c1402316fa8771e027fa2743664f3f137c764c13
This adds PowManager, as described in doc/dev/notes/service-side-pow.md,
hooks it into IptManager and Publisher, and adds code to publish and
rotate seeds, and to keep a updated list of Verifier instances for
currently active seeds.
tor-hscrypto: Implement Display for TimePeriod2025-03-13T18:22:40Zhjrgrn3874-hjrgrn@gitlab.torproject.org2025-03-13T18:22:40Zurn:sha1:fd21de5b82646524543dd2d5eae34b68fceeb91eRun maint/add_warning.2024-03-13T16:30:53ZNick Mathewsonnickm@torproject.org2024-03-13T16:30:53Zurn:sha1:c0c9bd15d42897825dd0ab3d3b8dd1c17bd6320ctor-hscrypto: Remove TimePeriodOffset, offset_within_period().2024-01-24T11:22:27ZGabriela Moldovangabi@torproject.org2024-01-23T18:43:02Zurn:sha1:f5ed0b92bc6c317d44a2b16bd4f19d77d6719006
These are now unused.
Part of #1166
tor-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
tor-hscrypto: Make offset_within_period() work with timestamps from later periods.2023-11-16T19:42:18ZGabriela Moldovangabi@torproject.org2023-11-16T19:31:03Zurn:sha1:d536ea8ae8e64e87b32c99deefb33ce05640ba16
Hidden services can have multiple "active" time periods for which they
generate descriptors. We need to be able to compute the offset of a
timestamp from the start of a given time period, even if that timestamp
falls within the "next" time period (for example, when publishing
descriptors for the "previous" time period, the `when` timestamp will
fall outside the `(start, end)` range of the "previous" time period).
Implementation for AES-based Order-preserving encryption2023-11-16T16:00:15ZNick Mathewsonnickm@torproject.org2023-11-16T01:40:28Zurn:sha1:ee85ed81c1bf51b8f58111804a91779ae6c1b061
This is the approach from appendix F.2 in rend-spec.
Part of #1053.
tor-hscrypto: Add a new constructor and an accessor for TimePeriod.2023-10-19T10:53:43ZGabriela Moldovangabi@torproject.org2023-10-11T15:29:53Zurn:sha1:e8aaa3fdd5040554cb9ffcf3e23aacaf97af58ector-hscrypto: Rename offset_in_sec to epoch_offset_in_sec.2023-10-19T10:53:43ZGabriela Moldovangabi@torproject.org2023-10-16T16:10:49Zurn:sha1:ebc853d29b02a5ef70acafdb775a35143c0d3d41
This renaming aims to make it clearer that this offset is _not_ the time
between start of the epoch and the start of this time period, but rather
the delta between our epoch and the Unix epoch, in seconds.