Skip to main content

Crate m4a_keys

Crate m4a_keys 

Source
Expand description

m4a’s keystore layer. m4a CONSUMES keys; the crypto is tesserax-keytree.

  • Standalone: Authority::Own — m4a holds its own root, issues session capabilities and signs letters itself.
  • Under an orchestrator: Authority::Delegated — m4a holds no root. Session keys live with the orchestrator’s keystore; m4a receives attenuated capabilities and signed letters and only verifies them against public keys (shared per room rules).

A session never signs as another: the signer takes the identity from the capability, and verify_letter binds the signature to the sender’s nick and public key.

Re-exports§

pub use tesserax_keytree as keytree;

Modules§

env
Environment names a session process sees (contract with the node; never renamed).
grants
m4a grants (namespace m4a).

Enums§

Authority
Who is the root of m4a’s keys.

Functions§

letter_message
Signed letter bytes: domain\0nick\0op\0payload. domain comes from the deployment.
verify_letter
Check a letter signed by a session key (own or delegated mode alike).