mirrors/arti.git/crates/tor-hscrypto/src/lib.rs, branch arti-v1.4.5

Temporarily suppress mismatched_lifetime_syntaxes.

2025-07-07T15:50:04Z

See #2060.

squash! Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

- The Rng::gen() functions have been renamed to Rng::random().

squash! Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

- The Standard distribution has been renamed to StandardUniform.

squash! Upgrade rand dependency to 0.9.

2025-03-18T16:09:44Z

- The rand::distributions module has been renamed to rand::distr

clippy: deny `mod_module_files`

2025-01-06T23:09:41Z

Denies 'mod.rs' files for consistency. https://rust-lang.github.io/rust-clippy/master/index.html#mod_module_files

add_warnings, *: Allow clippy::needless_lifetimes

2024-12-03T14:27:26Z

In 1.83, this warning triggers on many of our crates. We're thinking of fixing them all, but for now, we're going to disable the warning. This is part of #1765.

Rename "memquota" feature to "memquota-memcost" when it's just HasMemoryCost

2024-10-16T13:48:11Z

It's not documented anywhere ATM. I will do that in a followup MR.

hs-pow: Refactor to prefer stub types rather than cfg sprawl.

2024-10-09T16:05:15Z

In this design, the thin multiplexing layer between PoW types is always available when onion services are in use, but the specific pow schemes (and their dependency libraries) are gated by crate features everywhere. There are now no new cfg() gates. When the pow-v1 scheme is disabled, we can parse `pow-params v1` lines into an empty type (so clients know a PoW scheme exists that might be supported if they were configured differently). We currently don't save the contents of unknown hsdesc items. On the relaycell side, the hs ext module already sets a strong precedent for keeping unrecognized data as a byte vec, and it doesn't provide a good way to signal soft parse errors like unrecognized optional extensions. There, the `v1` type is completely optional, and services lacking a pow scheme suggested by a client would see one of these 'unrecognized' blobs. This isn't necessarily helpful but it fits the rest of the design. Co-authored-by: Micah Elizabeth Scott

tor-hspow: Big refactor, dissolve this crate

2024-10-09T16:04:35Z

My previous strategy here was to try and centralize hspow in one crate, writing it like a self-contained feature. That introduced friction in the data types, prompting the use of simplistic types at the netdoc/cell layers and full-featured types in the optional modules. This changes tactics, dissolving the low-level parts of tor-hspow into tor-hscrypto and the high-level parts into hsclient/hsservice. Full featured types are used everywhere now, but the tradeoff is that compile-time configurability is a lot more pervasive. Anything that knows about PoW types at all needs to be fully configured out. I took this opportunity to try a more complete set of crate features, allowing users to configure individual PoW schemes. Co-authored-by: Micah Elizabeth Scott

Some HasMemoryCost impls in tor-hscrypto

2024-10-02T18:11:26Z