Module cose 

This file contains private-use constants for COSE encoded key types and algorithms. Standardized values from https://www.iana.org/assignments/cose/cose.xhtml should always be preferred unless there is a a clear benefit, such as a clear cryptographic benefit, which MUST be documented publicly.

Re-exports

pub use thumbprint::CoseKeyThumbprint;

pub use thumbprint::CoseKeyThumbprintExt;

Modules

symmetric 🔒

COSE symmetric encryption — the middle layer of the three-layer stack:

thumbprint 🔒

RFC 9679 COSE Key Thumbprints.

Enums

CoseExtractError 🔒

SafeObjectNamespace 🔒

Constants

ALG_ARGON2ID13 🔒

ALG_PBKDF2_SHA256 🔒

PBKDF2-HMAC-SHA256 KDF algorithm discriminant, used by the password protected key envelope in the FIPS cipher suite. PBKDF2 is FIPS-approved, unlike Argon2id (ALG_ARGON2ID13).

ARGON2_ITERATIONS 🔒

ARGON2_MEMORY 🔒

ARGON2_PARALLELISM 🔒

ARGON2_SALT 🔒

CONTAINED_KEY_ID 🔒

Indicates for any object containing a key (wrapped key, password protected key envelope) which key ID that contained key has

CONTENT_TYPE_BITWARDEN_LEGACY_KEY 🔒

CONTENT_TYPE_PADDED_CBOR 🔒

CONTENT_TYPE_PADDED_UTF8 🔒

CONTENT_TYPE_SPKI_PUBLIC_KEY 🔒

PBKDF2_ITERATIONS 🔒

PBKDF2 iterations and salt, used by the password protected key envelope in the FIPS cipher suite.

PBKDF2_SALT 🔒

SAFE_CONTENT_NAMESPACE 🔒

Each type of object has it’s own namespace for strong domain separation to eliminate attacks which attempt to confuse object types. For signatures, this refers to signature namespaces, for data envelopes to data envelope namespaces and so on.

SAFE_OBJECT_NAMESPACE 🔒

MUST be placed in the protected header of cose objects

SIGNING_NAMESPACE 🔒

The label used for the namespace ensuring strong domain separation when using signatures.

SYMMETRIC_KEY 🔒

XAES_256_GCM 🔒

XAES-256-GCM (https://c2sp.org/XAES-256-GCM) extended-nonce AEAD. Given an input key and 192-bit nonce, a counter-based KDF is instantiated with CMAC-AES256, the input key, and the first 96 bits of the input nonce. The derived key and last 96 bits of the input nonce are then used to encrypt with AES-256-GCM.

XCHACHA20_POLY1305 🔒

XChaCha20 https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-xchacha-03 is used over ChaCha20 to be able to randomly generate nonces, and to not have to worry about key wearout. Since the draft was never published as an RFC, we use a private-use value for the algorithm.

Traits

ContentNamespace 🔒

CoseSerializable

Trait for structs that are serializable to COSE objects.

Functions

debug_key_operation 🔒

Helper function to convert a COSE KeyOperation to a debug string

extract_bytes 🔒

extract_integer 🔒