mirrors/arti.git/crates/tor-netdoc/src/doc/hsdesc.rs, branch arti-v1.4.6

netdoc: Add note about prop360

2025-07-10T13:41:48Z

netdoc: Tread a few more kinds of errors as suspicious.

2025-07-10T13:41:48Z

In particular, these are errors that provide an opportunity to inflate the size of an hsdesc download.

hs*: Define some HsDesc errors as _suspicious_.

2025-07-10T13:41:48Z

These errors are suspicious as hsdir inflation attacks, in the context of prop360.

TimerangeBound: Stop using std::ops::Bound.

2024-11-25T18:20:11Z

Fixes: #1691

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

First pass at implementing onion proof-of-work client

2024-10-09T16:04:35Z

This adds a module to tor-hspow for version-independent client logic. The entire module and its invocations are disabled unless the new "hs-pow" compile time feature is set. Co-authored-by: Micah Elizabeth Scott

tor-netdoc: Add parsing support for pow-params.

2024-10-09T16:04:35Z

This implements support for extensible proof-of-work parameters. Right now only a single type is defined, but in theory we can see up to one line per type on an onion service. Co-authored-by: Micah Elizabeth Scott

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

2024-10-03T11:42:19Z

Part of #1476

Upgrade to derive_more version 1.0.0

2024-09-25T14:37:18Z

The `derive_more` crate broke backward compatibility with this version, so this change involved quite a few manual fixups. With luck, they'll keep compatibility for some while in the future.