KeyType
Kinds of asymmetric keys, with their raw encodings. Every public key crossing the CryptoBackend boundary uses the encoding documented here; protocol code converts to and from wire formats.
The post-quantum types have two private-key encodings, told apart by length, so that every backend and every key format (COSE_Key, a key store) read the same bytes the same way: the seedLength-byte seed that key generation starts from, and the expandedPrivateKeyLength-byte expanded key the FIPS standards define. A software backend generates the seed, which is small and determines the whole key, and imports either.
Entries
Properties
Returns a representation of an immutable list of all enum entries, in the order they're declared.
For ML-KEM and ML-DSA, the length of the expanded private key: the decapsulation key dk = dk_PKE || ek || H(ek) || z of 768k + 96 bytes (FIPS 203 Algorithm 16, §8 Table 3) or sk = ρ || K || tr || s1 || s2 || t0 (FIPS 204 Algorithm 24, §4 Table 2). Null for the other types.
Raw public key length in bytes.
For ML-KEM and ML-DSA, the length of the seed that determines the private key: d || z of ML-KEM.KeyGen (64 bytes, FIPS 203 Algorithm 19) or ξ of ML-DSA.KeyGen (32 bytes, FIPS 204 Algorithm 1). Null for the other types, whose private keys have a single raw encoding.