mirrors/arti.git/crates/tor-hsservice/src/publish, branch arti-v1.4.6mirror of https://gitlab.torproject.org/tpo/core/arti
http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.62025-07-10T13:41:48Znetdoc, hsservice: Respect maximum descriptor sizes2025-07-10T13:41:48ZNick Mathewsonnickm@torproject.org2025-06-24T15:44:57Zurn:sha1:1df1014e9d52ae1c848f97daadfac4d7e1c61d36
It would be better to take a more sophisticated approach;
see #2048.
hs*: Define some HsDesc errors as _suspicious_.2025-07-10T13:41:48ZNick Mathewsonnickm@torproject.org2025-06-23T18:35:38Zurn:sha1:6ff683b2cf209ff0598efcdae7947ed6a8fbebbe
These errors are suspicious as hsdir inflation attacks, in the
context of prop360.
hs*: Include SourceInfo when making HsDesc requests.2025-07-10T13:41:48ZNick Mathewsonnickm@torproject.org2025-06-18T17:16:13Zurn:sha1:451fcbaac915b0662ffba7c3ff07f6c7ebde095e*: suppress cognitive_complexity warnings from nightly2025-05-29T14:21:17ZNick Mathewsonnickm@torproject.org2025-05-21T14:48:35Zurn:sha1:5327d3e22a83b8469a5d4191d92e1364344ddc93
Apparently clippy nightly is better (or worse?) about detecting
complex functions than before, so I'm suppressing these warnings
where they occur.
I have mixed feelings about these warnings: On the plus side,
they really do help to detect functions that are twistier than they
need to be. On the minus side, they get confused by tracing macros,
and the "allows" do pile up. But on the plus side, those "allows"
do provide a way to find functions that need to be refactored,
and they are never uglier than the functions they decorate.
tor-hsservice: Refactor PoW error handling.2025-05-27T18:05:01ZWesley Aptekar-Casselsme@wesleyac.com2025-05-06T20:45:20Zurn:sha1:f957b396065e5d77bfd942fb2e9fd88e0f646680
This adds a error type for internal errors, and in error cases where we
previously panicked, returns a Result instead. The publisher then simply
doesn't publish the pow_params line and warns the user.
tor-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.
Resolve clippy warnings from 1.832025-05-13T18:53:41ZNick Mathewsonnickm@torproject.org2025-05-13T18:53:41Zurn:sha1:b182a9d05902bc5320ab486d055521f18b6b7832
Now that our MSRV is 1.83, clippy is happy to make more
recommendations for us.
Use an EntropicRng trait to enforce key generation rules.2025-03-24T19:11:48ZNick Mathewsonnickm@torproject.org2025-03-20T15:09:08Zurn:sha1:8a33afe155e9bd29d9302b4b44dd5843d00866db
We want to require that whenever we generate a key that's persistent
(stored in KeyMgr), it's going to be made from a stronger-than-usual
Rng. This trait helps us enforce that.
We also add a FakeEntropicRng struct to use for testing.
Note that this turned up a case that we'd missed, which required
an internal change in tor-hsservice.
squash! Upgrade rand dependency to 0.9.2025-03-18T16:09:44ZNick Mathewsonnickm@torproject.org2025-03-18T13:01:31Zurn:sha1:2f8993c22c2b86010e4fd8b5169ef0ab83f8c754
- `rand::thread_rng()` has been deprecated and renamed to `rand::rng()`
tor-rt*: Apply deferred formatting churn2025-03-04T17:30:43ZIan Jacksonijackson@chiark.greenend.org.uk2025-02-26T18:13:00Zurn:sha1:39409be0db4def9ca5ffbd3bd14766112bcab527
rustfmt.