mirrors/arti.git/crates/tor-hscrypto/src, branch arti-v1.3.0

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: Effort type improvements.

2024-10-09T16:05:21Z

The Effort type didn't have any const constructor and we had to disassemble it to do any arithmetic. This adds a const constructor and int/float saturating arithmetic methods. Co-authored-by: Micah Elizabeth Scott

tor-hscrypto: Fixup broken doc links.

2024-10-09T16:05:21Z

Co-authored-by: Micah Elizabeth Scott

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

tor-hscrypto: Use the new "restricted discovery" terminology.

2024-10-03T11:42:29Z

Part of #1476

Some HasMemoryCost impls in tor-hscrypto

2024-10-02T18:11:26Z

tor_hsservice: add `impl From<&FooPublicKeySpecifier> for FooKeypairSpecifier` instances

2024-09-09T16:08:10Z

This adds the following trivial `From` instances: - tor_hsservice: impl From<&HsIdPublicKeySpecifier> for HsIdKeypairSpecifier - tor_hsservice: impl From<&BlindIdPublicKeySpecifier> for BlindIdKeypairSpecifier - tor_hscrypto::pk: impl From for HsBlindIdKey - tor_llcrypto::pk::ed25519: impl From for PublicKey - tor_keymgr::mgr: impl From for TestPublicKey - tor::hscrypto::pk: impl From for HsIdKey

tor-hscrypto: Implement Eq for HsClientDescEncKey.

2024-08-05T16:41:15Z

Needed because such keys will be stored in the `OnionServiceConfig`.

tor-hscrypto: Use collect_tuple to avoid unnecessary Vec allocation.

2024-07-08T17:25:59Z