SecretSharingAlgos class

Registry of the algorithm identifiers used in per-APKAM key packages and secret envelopes.

These ids exist for crypto agility: a key package advertises which algorithms its X-Wing public key supports, envelopes record which algorithms were used to protect a payload, and readers ignore entries whose ids they do not recognise. Adding a new suite later is just a matter of appending new ids to the supported lists — no schema or protocol change.

Annotations

• @experimental

Properties

hashCode → int

The hash code for this object.

no setter, inherited

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited

Constants

keyAlgos → const List<String>

Key-establishment algorithms this client supports, strongest first. A sender picks the first of these that the recipient's key package advertises.

suites → const List<String>

Sealing suites this client can produce and open, strongest first.

useEnc → const String

The use value for key-package keys whose purpose is establishing content keys (KEM encapsulation).

xWing → const String

X-Wing hybrid post-quantum/traditional KEM (draft-connolly-cfrg-xwing-kem-10; X25519 + ML-KEM-768). A key package's advertised key is an X-Wing public key; a sender encapsulates to it. IND-CCA holds if either component survives, so confidentiality is harvest-now-decrypt-later resistant.

xWingHpke → const String

HPKE-style sealing suite — X-Wing KEM + HKDF-SHA256 + AES-256-GCM, as implemented by at_chops pqSeal/pqOpen. The envelope's sealed field carries the whole construction (KEM ciphertext, the HKDF-derived AEAD key schedule, authenticated ciphertext and tag); the envelope's suite field records which construction produced it.