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

Fix name of clippy lint to unchecked_time_subtraction (2)

2025-11-06T11:28:22Z

Run maint/add_warning

Remove "doc_auto_cfg" incantation from all crates.

2025-09-29T19:30:03Z

This feature has been removed from nightly, in favor of doc_cfg.

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