Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

specify how to handle multiple olm sessions with the same device #1596

Merged
merged 2 commits into from
Aug 30, 2018
Merged

specify how to handle multiple olm sessions with the same device #1596

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
688c8eb
specify how to handle multiple olm sessions with the same device
uhoreg Aug 29, 2018
9d0fec3
add changelog
uhoreg Aug 29, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelogs/client_server/newsfragments/1596.clarification
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
specify how to handle multiple olm sessions with the same device
6 changes: 6 additions & 0 deletions specification/modules/end_to_end_encryption.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -391,6 +391,12 @@ this check, a client cannot be sure that the sender device owns the private
part of the ed25519 key it claims to have in the Olm payload.
This is crucial when the ed25519 key corresponds to a verified device.

If a client has multiple sessions established with another device, it should
use the session from which it last received a message. A client may expire old
sessions by defining a maximum number of olm sessions that it will maintain for
each device, and expiring sessions on a Least Recently Used basis. The maximum
number of olm sessions maintained per device should be at least 4.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if 4 is the right number here, but I think that it will handle the case where two clients keep alternating between two sessions because they send each other messages at the same time, and then they both decide that they need to start new sessions (e.g. because the old sessions are wedged).


``m.megolm.v1.aes-sha2``
~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down