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

Jump to bottom

Unencrypted messages after encryption was turned on. #12313

Closed
madduck opened this issue Feb 11, 2020 · 1 comment
Closed

Unencrypted messages after encryption was turned on. #12313

madduck opened this issue Feb 11, 2020 · 1 comment
Labels
A-E2EE T-Defect X-Needs-Community-Testing

Comments

@madduck
Copy link

madduck commented Feb 11, 2020

image

My colleague turned on encryption. The next couple of messages I sent from Riot-Web still went unencrypted. Then, a message sent from Android to the room was encrypted properly. And when I went to create this bug report, also Riot-Web sent encrypted messages.

Maybe the keys took a bit longer to exchange, but Riot should definitely not claim that it turned on encrypted, and then proceed to send unencrypted messages.

riot-web version: 1.5.7.9
olm version: 3.1.3
FF: 72.0.2
@ara4n ara4n mentioned this issue Nov 8, 2020
Closed
@kittykat
Copy link
Contributor

I'm going to close this issue as we cannot reproduce it any more. If you are still experiencing it, please comment with @kittykat and I will reopen it.

t3chguy pushed a commit that referenced this issue Oct 17, 2024
@renovate
Update dependency @sentry/browser to v7.104.0 (#12313)
2f6e967 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-E2EE T-Defect X-Needs-Community-Testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kittykat @madduck @jryans