lockbitchat
e3e10656d7
The README, ARCHITECTURE.md and CRYPTOGRAPHY.md still described the old handshake: keys and a session salt travelling inside the invitation, and a safety code derived from the two DTLS fingerprints. None of that has been true since 5.9.0. Adds a "The invitation" section to the README covering what the exchange was reduced to and why that is a security change and not only a smaller QR code: less material exposed before anyone is authenticated, the DTLS fingerprint as the anchor, substituted keys failing closed on the commitment instead of on a human comparison, a safety code that now covers the whole transcript rather than two fingerprints, and the plain fact that a single QR is scanned in person where a four-frame animated one pushes people to paste the invitation through a chat app. Session lifecycle in ARCHITECTURE.md gains the in-band key exchange as its own step. CRYPTOGRAPHY.md now states that the salt is derived from the transcript rather than transmitted, and describes the transcript SAS and the signature that replaced the challenge/response. DESCRIPTOR-SBQ2.md is listed in the doc index and in the CONTRIBUTING impact table.
10 lines
263 B
JSON
10 lines
263 B
JSON
{
|
|
"version": "1786056807121",
|
|
"buildVersion": "1786056807121",
|
|
"appVersion": "5.9.0",
|
|
"buildTime": "2026-08-06T22:53:27.174Z",
|
|
"buildId": "1786056807121-7754f6b",
|
|
"gitHash": "7754f6b",
|
|
"generated": true,
|
|
"generatedAt": "2026-08-06T22:53:27.175Z"
|
|
} |