mirrors/arti.git/crates/tor-relay-crypto, branch arti-v1.2.8

Bump arti- and tor- crates to 0.23.0

2024-09-30T13:04:32Z

Per our policy, every one of these gets a minor bump. Generated with: ``` for crate in $(./maint/list_crates | grep '^$tor\|arti$-' ); do cargo set-version --bump minor -p $crate; done ``` (Note the use of `-` at the end end of the grep pattern to prevent matching the `arti` crate.)

Merge branch 'msrv-1.77-and-rusqlite-update' into 'main'

2024-09-26T14:24:02Z

Upgrade MSRV to 1.77 , and rusqlite to 0.32.1 See merge request tpo/core/arti!2451

Merge branch 'upgrades-20240925' into 'main'

2024-09-26T12:07:09Z

Upgrade dependencies in preparation for next week's releases. See merge request tpo/core/arti!2450

Upgrade MSRV to 1.77

2024-09-26T01:54:22Z

This will allow us to upgrade to the latest version of rusqlite.

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.

Run fixup-features in preparation for upcoming release.

2024-09-25T14:06:30Z

tor-key-forge: encapsulate `define_ed25519_keypair` macro deps

2024-09-18T19:27:33Z

This re-exports the types/traits needed by the `define_ed25519_keypair` macro so that the macro caller doesn't need to import a bunch of extra packages in its Cargo.toml that it doesn't use, and so that the caller doesn't need a `use prelude::*` before invoking the macro. This makes the macro nicer to use for the caller, and should prevent the macro from causing "cannot find ... in this scope" errors.

key-forge: Support extra docs and attributes to ed25519 keypair

2024-09-18T13:24:04Z

Signed-off-by: David Goulet

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