Re-exports§
pub use key_encryptable::CryptoKey;pub use key_encryptable::KeyContainer;pub use key_encryptable::KeyDecryptable;pub use key_encryptable::KeyEncryptable;pub use master_key::HashPurpose;pub use master_key::MasterKey;pub use symmetric_crypto_key::Aes256CbcHmacKey;pub use symmetric_crypto_key::Aes256CbcKey;pub use symmetric_crypto_key::EncodedSymmetricKey;pub use symmetric_crypto_key::SymmetricCryptoKey;pub use symmetric_crypto_key::XChaCha20Poly1305Key;pub use asymmetric_crypto_key::AsymmetricCryptoKey;pub use asymmetric_crypto_key::AsymmetricPublicCryptoKey;pub use asymmetric_crypto_key::PublicKeyEncryptionAlgorithm;pub use signed_public_key::SignedPublicKey;pub use signed_public_key::SignedPublicKeyMessage;pub use user_key::UserKey;pub use device_key::DeviceKey;pub use device_key::TrustDeviceResponse;pub use pin_key::PinKey;pub use kdf::dangerous_derive_kdf_material;Deprecated pub use kdf::Kdf;pub use kdf::default_argon2_iterations;pub use kdf::default_argon2_memory;pub use kdf::default_argon2_parallelism;pub use kdf::default_pbkdf2_iterations;
Modules§
- asymmetric_
crypto_ 🔒key - device_
key 🔒 - kdf 🔒
- key_
encryptable 🔒 - key_id 🔒
- master_
key 🔒 - pin_key 🔒
- shareable_
key 🔒 - signed_
public_ 🔒key - A public encryption key alone is not authenticated. It needs to be tied to a cryptographic identity, which is provided by a signature keypair. This is done by signing the public key, and requiring consumers to verify the public key before consumption by using unwrap_and_verify.
- symmetric_
crypto_ 🔒key - user_
key 🔒 - utils 🔒