mirrors/arti.git/Cargo.toml, branch arti-v1.3.1

tor-connect-point: new crate to manage RPC connect points

2024-11-19T19:33:46Z

See doc/dev/rpc-book/src/rpc-connect-sketch.md for details.

cargo: reorder workspace members

2024-11-04T15:17:07Z

Merge branch 'tor-genaddr' into 'main'

2024-10-29T22:05:15Z

Extract general::SocketAddr and its unix friends to their own crate. See merge request tpo/core/arti!2592

Extract general::SocketAddr and its unix friends to their own crate.

2024-10-29T17:25:48Z

This is mostly code motion.

tor-config-path: added empty package

2024-10-29T14:48:05Z

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

Bump tor-units up the crate stack

2024-10-02T18:11:26Z

We're going to need this to use tor-memquota.

add example: axum router as onion service

2024-09-24T19:56:04Z

relay-crypto: Initial import of new tor-relay-crypto crate

2024-09-18T13:24:04Z

This adds a new crate called tor-relay-crypto which is responsible for declaring the relay keys and certificate that will be used by a relay and stored in a KeyMgr. This is in its own crate and considered pretty low level so other crates can use it to access the relay keys, like tor-proto, for cryptographic actions like channel authentication or descriptor signing. The lower level cryptographic keys are wrapped in a higher level object in this crate, using tor-key-forge crate, so we can have proper semantic and strong type check on those keys so they are not misused or confused with other keys. At this point, the key declaration might change once the KeyMgr supports attaching a certificate to a key. We are likely going to see more code related to certificate creation in this crate in the future. Part of #1604 Signed-off-by: David Goulet

Rename tor-keys crate to tor-key-forge

2024-09-04T18:26:37Z

Signed-off-by: David Goulet