Expand description
Numbers a phone and a leaf node must configure identically.
Each of these is a value that appears on both sides of a sealed conversation. A copy that drifts does not fail a build or a test: it produces a peer that is configured differently from the one it is talking to, and the symptom arrives later, on a device, as a message that will not decrypt.
Constants§
- ACK_
FOR_ KEY - The metadata key naming the message a delivery acknowledgement answers.
- LEAF_
KEY_ PACKAGE_ LIFETIME - How long a leaf node’s key package claims to be valid.
- LEAF_
KEY_ PACKAGE_ NOT_ BEFORE_ BACKDATE_ SECONDS - How far into the past a leaf’s key package validity window has to start.
- LEAF_
SENDER_ RATCHET_ MAXIMUM_ FORWARD_ DISTANCE - How far ahead a leaf node’s receiver ratchet may be fast-forwarded: a frame more than this many generations past the next one it expects is refused.
- MAX_
ACCEPTED_ KEY_ PACKAGE_ LIFETIME - The widest validity window this SDK will admit in a key package it did not mint, at import and on every read of the cache.
- SENDER_
RATCHET_ MAXIMUM_ FORWARD_ DISTANCE - How far ahead of the highest seen generation a sender ratchet may be fast-forwarded when messages are lost.
- SENDER_
RATCHET_ OUT_ OF_ ORDER_ TOLERANCE - How many generations behind the latest decrypted message a sender ratchet key is kept, so late/reordered messages remain decryptable.