You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v6.3.0 — Media end-to-end encryption, room and profile access control
This commit was created on GitHub.com and signed with GitHub’s verified signature.
v6.3.0 (Latest) — Media end-to-end encryption: files encrypted with the room key, members-only media links
Files (photos, voice, video) are now encrypted with the room key before upload (PQF1 + AES-256-GCM); the server only ever stores ciphertext. The message ratchet is untouched — the file key comes from stable per-room material.
Media links open only for logged-in members of that chat: /api/media requires a session token and room membership; the public /uploads route is gone; deleted messages' media is denied; orphan media is denied. Avatars stay visible to logged-in users (public profile pictures by design, never anonymous).
Old media: access-controlled through its message's room, but NOT encrypted — the server never had the key, so it cannot retro-encrypt. Re-upload a file to encrypt it.
Room and profile access control: /api/messages/:roomId now requires a session and room membership; /api/groups/:username, /api/contacts/:username, POST /api/user/update and POST /api/add-contact now require a session and only let a user act on their own data (anyone could previously read any room's messages or overwrite any user's profile).
123/123 tests pass.
Known limits: the 1:1 file key is ECDH-derived (classical) — the PQ ratchet key is wiped on every rekey and cannot serve as a stable file key; group files use the ML-KEM-distributed epoch key. A member can still re-share a decrypted file outside the app.