#tor #arti


Key management for the Arti Tor implementation

5 releases (3 breaking)

0.4.0 Oct 31, 2023
0.3.0 Oct 2, 2023
0.2.1 Sep 5, 2023
0.2.0 Aug 1, 2023
0.1.0 Jun 30, 2023

#970 in Cryptography

Download history 177/week @ 2023-07-28 164/week @ 2023-08-04 137/week @ 2023-08-11 157/week @ 2023-08-18 165/week @ 2023-08-25 215/week @ 2023-09-01 144/week @ 2023-09-08 161/week @ 2023-09-15 94/week @ 2023-09-22 214/week @ 2023-09-29 122/week @ 2023-10-06 158/week @ 2023-10-13 248/week @ 2023-10-20 285/week @ 2023-10-27 197/week @ 2023-11-03 305/week @ 2023-11-10

1,061 downloads per month
Used in 9 crates (3 directly)


12K SLoC


Code to fetch, store, and update keys.


This crate is part of Arti, a project to implement Tor in Rust.

Likely to change

The APIs exposed by this crate (even without the keymgr feature) are new and are likely to change rapidly. We'll therefore often be making semver-breaking changes (and will update the crate version accordingly).

Key stores

The KeyMgr is an interface to one or more key stores. The key stores are types that implement the Keystore trait.

This crate provides the following key store implementations:

  • Arti key store: an on-disk store that stores keys in OpenSSH format.
  • (not yet implemented) C Tor key store: an on-disk store that is backwards-compatible with C Tor (new keys are stored in the format used by C Tor, and any existing keys are expected to be in this format too).

In the future we plan to also support HSM-based key stores.

Key specifiers and key types

The Keystore APIs expect a "key specifier" (specified for each supported key type via the KeySpecifier trait), and a KeyType.

A "key specifier" identifies a group of equivalent keys, each of a different type (algorithm). It is used to determine the path of the key within the key store (minus the extension).

KeyType represents the type of a key (e.g. "Ed25519 keypair"). KeyType::arti_extension specifies what file extension keys of that type are expected to have (when stored in an Arti store).

The KeySpecifier::arti_path and KeyType::arti_extension are joined to form the path of the key on disk (relative to the root dir of the key store). This enables the key stores to have multiple keys with the same role (i.e. the same KeySpecifier::arti_path), but different key types (i.e. different KeyType::arti_extensions).

KeySpecifier implementers must specify:

  • arti_path: the location of the key in the Arti key store. This also serves as a unique identifier for a particular instance of a key.
  • ctor_path: the location of the key in the C Tor key store (optional).

Feature flags

Additive features

(None yet.)

Experimental and unstable features

Note that the APIs enabled by these features are NOT covered by semantic versioning[^1] guarantees: we might break them or remove them between patch versions.

  • keymgr -- build with full key manager support. Disabling this feature causes tor-keymgr to export a no-op, placeholder implementation.

[^1]: Remember, semantic versioning is what makes various cargo features work reliably. To be explicit: if you want cargo update to only make safe changes, then you cannot enable these features.


~362K SLoC