| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | cargo: tor-hscrypto: Declare pow-* experimental | Ian Jackson | 2024-10-30 | 1 | -0/+13 |
| | | | | | | We need to add the experimental feature, and the corresponding section in the README.md. | ||||
| * | cargo: tor-hscrypto: Move `full` earlier in README.md | Ian Jackson | 2024-10-30 | 1 | -2/+2 |
| | | | | | This makes space to introduce the experimental section. | ||||
| * | tor-hscrypto: Document Cargo features | Ian Jackson | 2024-10-22 | 1 | -1/+18 |
| | | |||||
| * | tor-hspow: Big refactor, dissolve this crate | Wesley Aptekar-Cassels | 2024-10-09 | 1 | -0/+2 |
| | | | | | | | | | | | | | | | | | | 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 <[email protected]> | ||||
| * | hscrypto: write a README | Nick Mathewson | 2023-06-13 | 1 | -1/+20 |
| | | |||||
| * | Create a new tor-hscrypto crate. | Nick Mathewson | 2023-01-06 | 1 | -0/+8 |
| This module has types and operations needed in multiple places for an onion service implementation. There are a bunch of TODO hs-crypto comments that we'll need to fill in. | |||||
