mirrors/arti.git/crates/tor-hsservice/src/svc/publish.rs, branch ios-sqlite-hacksmirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=ios-sqlite-hacks2023-09-13T11:37:11Ztor-hsservice: Introduce helpers for implementing a backoff schedule.2023-09-13T11:37:11ZGabriela Moldovangabi@torproject.org2023-09-08T18:03:40Zurn:sha1:3b818507a0d0695ff2a9171ffd3b5837742752bdtor-hsservice: Remove unused Event struct (fmt).2023-09-06T15:15:01ZGabriela Moldovangabi@torproject.org2023-09-06T15:15:01Zurn:sha1:cda9bb39123a5b791733468b71c91fa7882a4c03tor-hsservice: Remove unused Event struct.2023-09-06T15:14:06ZGabriela Moldovangabi@torproject.org2023-09-06T15:12:21Zurn:sha1:89d8dce4a4ae753c2490368f143b90718924a879
The reactor events are no longer received on the same channel, so we
don't need the `Event` enum or the old `Publisher` APIs any more.
Svc config changes are received on a wseparate `postage::watch` channel,
whereas IPT changes are detected through the `IptsPublisherView`.
The publisher will (eventually) be informed of keystore changes through
another `postage::watch` channel.
tor-hsservice: Use a postage::watch channel to watch for config changes.2023-09-06T15:09:46ZGabriela Moldovangabi@torproject.org2023-09-06T15:08:09Zurn:sha1:2d31087bb55c0ca35bd0f1f99c2ef6b040a0f7c7
If multiple config changes happen in quick succession, we don't want the
publisher to publish a new descriptor for every single one.
tor-hsservice: Use the new IPT change notifier API (fmt).2023-09-06T15:04:43ZGabriela Moldovangabi@torproject.org2023-09-06T15:04:43Zurn:sha1:71806b83cd7186cbab3189a200a379bab8fbaab4tor-hsservice: Use the new IPT change notifier API.2023-09-06T15:01:52ZGabriela Moldovangabi@torproject.org2023-09-06T15:01:52Zurn:sha1:246d098a4ac91f737a28da1e24a308c658536f6e
This makes the publisher watch for IPT changes using the
`IptsPublisherView` added in arti#1023 (instead of waiting for an
`Event::NewIntroPoints`. The `Event` enum will soon be replaced by
multiple `postage::watch` channels, one for every type of change it
needs to react to).
tor-hsservice: Move PublishIptSet and its pieces into a new module2023-09-06T14:21:01ZIan Jacksonijackson@chiark.greenend.org.uk2023-09-06T13:16:42Zurn:sha1:d66ed0fc7ba31985f0e8c99a4d21b61d2c87146a
This is going to be complicated enough we probably want it split out
of the publisher.
tor-hsservice: publish: Add type alias for PublishIptSet2023-09-05T10:32:07ZIan Jacksonijackson@chiark.greenend.org.uk2023-09-05T10:10:00Zurn:sha1:5d10f343f88a95500631c7761afb70341c78e6c9tor-hsservice: Fix type of descriptor lifetime in IptSet2023-08-30T15:42:06ZIan Jacksonijackson@chiark.greenend.org.uk2023-08-30T15:42:06Zurn:sha1:4fd92335cbb5a71e9c04b3544ecf9341e4321cb7
As per
https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/1559#note_2937976
tor-hsservice: Have the manager be in charge of expiry time2023-08-29T16:53:32ZIan Jacksonijackson@chiark.greenend.org.uk2023-08-29T13:43:43Zurn:sha1:e48588a8f16591f9d38d115651fdd37458199a42
Add the expiry time (as wall clock time) to publish::IptSet.
The manager is in a good position to know this information.
Provide constants that will be used (for now) for actually calculating
the expiry times.
(Right now the part where the expiry time would actually be calculated
doesn't exist, but it will come soon.)