mirrors/arti.git/crates/tor-hscrypto/src/time.rs, branch arti-v1.1.11mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.1.112023-11-16T19:42:18Ztor-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.
Run maint/add_warning to add lint block everywhere2023-08-23T09:34:00ZIan Jacksonijackson@chiark.greenend.org.uk2023-08-22T14:28:12Zurn:sha1:42df88d6bf6dbb460d2e5e1cd4838aafaffbe9acRun maint/add_warning to actually apply new lint allows2023-07-10T12:49:51ZIan Jacksonijackson@chiark.greenend.org.uk2023-07-10T11:19:32Zurn:sha1:473447a82e099fd52a674c28f5bc24b3e05208c0hscrypto: fix TODOs in time-period code.2023-06-13T16:39:52ZNick Mathewsonnickm@torproject.org2023-06-13T16:37:31Zurn:sha1:0add7df458f36831723e1679bfe4681b94d15042
* Return a more informative error type (instead of Option)
* Check that time periods are an integer number of seconds
* Decide not to change the semantics of an argument.
hscrypto: remove compatibility note about time periods.2023-06-13T16:20:12ZNick Mathewsonnickm@torproject.org2023-06-13T16:20:12Zurn:sha1:0a4dac0fa0763a747e0ed709dbe6f51df1861df1
We updated and clarified the spec in arti!107, and noted the
remaining infelicities in proposal 342.
hs time handling: Make TimePeriod contain length as IntegerMinutes2023-02-09T12:56:18ZIan Jacksonijackson@chiark.greenend.org.uk2023-02-08T17:35:51Zurn:sha1:4626ccfcaaf71ee364e71447b2a548d5f3f504c4
Locally, the only functional effect is that now we refuse to handle
non-whole-number-of-minutes lengths - but since the consensus
parameter can't represent those, there's no overall functional change.
netdir: Implement ring-param constructors and time period accessors2023-01-28T17:43:08ZNick Mathewsonnickm@torproject.org2023-01-24T15:46:56Zurn:sha1:5236c5cf887af0bd321ca80fb6dba991289549d6
This logic is a bit tricky, so I've tried to document it and add
fairly good tests. The silver lining is that the external API for
all of this logic will make it invisible and hidden.
There are some cases where I added functions that I think might
eventually get lowered into MdConsensus: But I don't want to lower
too much right now, since the convention for our netdoc accessors is
that they are fairly unsophisticated, and they show you the document
as it is.
Closes #686