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
While trying to automatically create large populated E2E encrypted rooms for testing we encountered following scenario:
A number of users is created and logged in with backup creation via passphrase
All those users (Bs) are logged out again
Another user (A) creates an e2e encrypted room and invites all Bs
The Bs log in one after another in a private browser session and accept the invitation afterwards the browser is closed but the user not logged out (a session should remain)
A sends a message in the room
The Bs open the browser again
The Message from A is encrypted
Outcome
What did you expect?
The Bs can read the message from A because all of them had an open session (even without dehydrated session)
What happened instead?
The Message stays encrypted for the Bs
Operating system
Does not matter
Browser information
Does not matter
URL for webapp
both app.element.io and develop.element.io
Application version
Version von Element: 1.11.61 Krypto-Version: Rust SDK 0.7.0 (b1918e9), Vodozemac 0.5.1
Homeserver
matrix.org
Will you send logs?
No
The text was updated successfully, but these errors were encountered:
The receiver accounts (Bs) are all logged in when the user A send the message (See the point 4: "The Bs log in one after another in a private browser session and accept the invitation afterwards the browser is closed but the user not logged out (a session should remain)).
Just because the session remains on the server, doesn't mean it does on the client. Private browser sessions are amnesiac. I believe it to be a duplicate of the PFS issue but if you're not happy with that feel free to have it as a duplicate of element-hq/element-meta#245
Steps to reproduce
While trying to automatically create large populated E2E encrypted rooms for testing we encountered following scenario:
Outcome
What did you expect?
The Bs can read the message from A because all of them had an open session (even without dehydrated session)
What happened instead?
The Message stays encrypted for the Bs
Operating system
Does not matter
Browser information
Does not matter
URL for webapp
both app.element.io and develop.element.io
Application version
Version von Element: 1.11.61 Krypto-Version: Rust SDK 0.7.0 (b1918e9), Vodozemac 0.5.1
Homeserver
matrix.org
Will you send logs?
No
The text was updated successfully, but these errors were encountered: