Repository navigation
Releases
Sirr v1.2.0
Fixes for four reports received through GitHub's private vulnerability reporting. Thanks to KineticEnforcer for a careful source review.
Protocol change: 1.2.0 does not talk to 1.1.x. A 1.1 peer is refused with "peer runs an older Sirr". Accepting old peers would let anyone in the path downgrade a link back to readable frames, so everyone in a room needs to update.
High — bridges could read and forge most traffic (GHSA-mmqx-xg3q-gxpf)
With a WebSocket bridge in the path, the Noise transport ends at the bridge. 1.1.0 encrypted chat bodies, profiles, files, edits and room keys end to end, but sent voice audio and signaling, pins (with message previews), room and channel names, typing, admin and charter updates, sync summaries and membership updates as plain frames inside the transport — readable and injectable by a bridge operator. SECURITY.md said otherwise; that was wrong.
- Every frame after the handshake now travels in one sealed record type. Nothing but the handshake is accepted in the clear; there is no list of "encrypted types" left for a new message to fall out of.
- Frames written before the session exists are held and sent sealed once it does.
- SECURITY.md and PROTOCOL.md now state exactly what a bridge still sees: the handshake (identity public key, room tags), file-transfer frame headers, and record sizes and timing.
Moderate — no per-message key evolution (GHSA-fwx8-fgvh-j8w5)
1.1.0 used one session key per connection for its whole life.
- Per-direction hash ratchet: a fresh key for every record, wiped after use. Keys copied from memory open nothing already sent.
- Record counters: replayed, reordered, rewritten or forged records are refused and end the session.
- In-session X25519 rekey every 10 minutes (or 5000 records): someone who copied the keys but isn't on the wire is locked out again.
- File transfers: each offer carries its own random salt inside the ratcheted session; transfer keys no longer derive from a per-connection key alone.
Moderate — "sig ok" was shown without checking the signature (GHSA-jj3h-r5mp-jjc4)
Live messages displayed "sig ok" on the strength of the authenticated session, without verifying the room signature they carried.
- Live messages and edits are now verified against the author's room key on arrival. "sig ok" appears only for a signature that checked out (or your own messages); a failing or uncheckable signature shows nothing, and a bad one is logged.
Low — hardening bundle (GHSA-g44g-rx4g-rpwr)
- Voice is only sent once the session exists, matching what the receiver accepts.
- Room permissions fail closed: a room whose code commits to no owner grants nobody rights, and the settings UI no longer offers owner controls that enforcement would refuse (SR- rooms before their charter arrived showed them to everyone).
- Temporary identity: when the saved identity can't be unlocked (OS keyring unavailable), Sirr now keeps the temporary identity in memory only and shows a permanent banner. 1.1.0 also overwrote the saved identity with the temporary one (keeping the old file as
identity.json.locked); that no longer happens. If you were hit by this, see "Recovering" below. sirr://links ask before joining: the dialog shows the room code; nothing is announced until you click Join. Codes typed or pasted in the app still join at once.- Edits are capped like new messages (8000 characters) on the network, in the event handler and in the store.
Recovering an identity overwritten by 1.1.0
If 1.1.0 ever started with a locked keyring, your original identity is in identity.json.locked in Sirr's data folder (~/.sirr; on Windows %USERPROFILE%\.sirr). Quit Sirr, unlock your keyring, rename identity.json to identity.json.temp and identity.json.locked to identity.json, then start Sirr.
Windows: Sirr-Setup-*.exe installs Sirr; Sirr-*-portable.exe runs without installing.
Linux: Sirr-*-x86_64.AppImage (chmod +x, run) or Sirr-*-amd64.deb (sudo apt install ./Sirr-*-amd64.deb).
Builds are not code-signed yet. Check the file against SHA256SUMS.txt before running it:
sha256sum -c SHA256SUMS.txt --ignore-missing (Linux) · certutil -hashfile <file> SHA256 (Windows).
Full Changelog: v1.1.0...v1.2.0
Sirr v1.1.0
Windows: Sirr-Setup-*.exe installs Sirr; Sirr-*-portable.exe runs without installing.
Linux: Sirr-*-x86_64.AppImage (chmod +x, run) or Sirr-*-amd64.deb (sudo apt install ./Sirr-*-amd64.deb).
Builds are not code-signed yet. Check the file against SHA256SUMS.txt before running it:
sha256sum -c SHA256SUMS.txt --ignore-missing (Linux) · certutil -hashfile <file> SHA256 (Windows).
Full Changelog: https://github.com/CRTnoise/sirr/commits/v1.1.0