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.

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

Olm sessions imported from legacy crypto will always be used in preference to newer olm sessions #8719

Closed
richvdh opened this issue Dec 22, 2023 · 1 comment · Fixed by #8838
Labels

Comments

@richvdh
Copy link
Member

richvdh commented Dec 22, 2023

Background: If an Olm session "wedges", we will attempt to work around it by starting a new session. Later, when either side wants to send another olm message, it will use the most recent Olm session -- ie, the new session.

However: when sessions are imported from legacy crypto, their "creation_time" and "last_used_time" are both set 50000 years in the future. (They are set in milliseconds rather than seconds. See also matrix-org/matrix-rust-sdk#2974, matrix-org/matrix-rust-sdk#2973.) That means that the imported session will always be used in preference to any newer sessions.

@richvdh
Copy link
Member Author

richvdh commented Dec 22, 2023

element-ios has the same bug: element-hq/element-ios#7727 no it doesn't

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants