Expand description
The channel of a signed exec session, without any network code.
- The enforcer sends a
Challenge: a fresh nonce and an ephemeral X25519 key for this session. - The engineer’s device signs a
session/v1statement naming that nonce, that key and the client’s own ephemeral key. - Both sides run
Noise_KK_25519_ChaChaPoly_SHA256with the two keys, bound to the statement’s digest, so the session is the one that was signed. Every later frame is encrypted and numbered: whoever relays the frames reads nothing, and a frame it injects, drops, reorders or replays fails to decrypt. - The enforcer appends every frame to a hash-chained
Transcript.
Structs§
- Challenge
- What the enforcer sends first.
- Channel
- An encrypted, numbered channel.
- Handshake
- One side of the handshake, before it completes.
- Session
Body session/v1: one exec session.- Session
Challenge - What the enforcer handed out for one session request.
- Session
Keys - An X25519 key pair for one session.
- Session
Target - What a session runs.
- Transcript
- A hash-chained transcript of one session.
- Transcript
Entry - One transcript entry. Each names the hash of the one before, so an entry that is removed or changed breaks the chain.
Enums§
- Direction
- Direction of a transcript entry.
- Frame
Kind - What one frame carries.
- Side
- Which side of the channel this is.
Constants§
- MAX_
FRAME_ PAYLOAD - Plaintext room in one Noise message, after the tag and the frame kind.
- MAX_
SESSION_ SECONDS - Longest exec session a statement may allow.
- NONCE_
LIFETIME_ SECONDS - How long a challenge’s nonce stays usable.
Functions§
- verify_
transcript - Check that
entriesform one unbroken chain from the statement.