Session crypto transparency: encrypted echo bot with 0 new lines #28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
§10.4.2 transparency contract: decryption transparent in every event surface (typed/raw; UTD states, never fake content — CR-6); encryption transparent on send; refuse-plaintext guard holds with typed error (CR-7, §2.5); crypto constructed with the session — no init-ordering trap. M1 exit criterion: the same echo bot works in an encrypted room with 0 new lines (CR-20). Crypto-store failure wedges typed, never downgrades to plaintext (§10.4.6, §9).
Discovered while scoping #27: engine-side wiring this issue needs — SyncBatch currently carries only toDevice; it lacks device_lists (changed/left), device_one_time_keys_count and device_unused_fallback_key_types. Extending SyncBatch means touching both sources (SyncV2Source.parse, SlidingSyncSource) and the replay corpus fact hash. Also still missing engine-side: keys/upload, keys/query, keys/claim, sendToDevice endpoint definitions in katrix-core Endpoints. The machine's input type (CryptoSyncChanges, katrix-crypto) is defined by #27 and ready to be fed.