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

end-to-end encryption is broken #3780

Closed
barpaw opened this issue Oct 31, 2020 · 0 comments
Closed

end-to-end encryption is broken #3780

barpaw opened this issue Oct 31, 2020 · 0 comments

Comments

@barpaw
Copy link
Contributor

barpaw commented Oct 31, 2020 •
edited
Loading

Everyone knows e2e encryption is not working properly on element-ios client.

Encryption/Decryption in WEB and Android clients works fine.

You get a lot of bug reports related to incorrect decryption of messages (UISIs) that occur in the ios client.

Why do you implement new things when the CORE functionality related to message encryption/decryption does not work?
Are your French government customers not complaining about this bugs?

I am asking you to focus on fixing CORE bugs related to message decryption (BAD_MESSAGE_KEY_ID , Unknown inbound session id BAD_MESSAGE_MAC). Focus on fixing things related to OTKs.

Also i found this fix #3721 does not resolve the issue of re-uploading the same keys. This bug still exists and leads to UISIs , BAD_MESSAGE_KEY_ID and Crypto failed to start. Error.
@barpaw barpaw changed the title One time keys upload can try to upload the same key again end-to-end encryption is broken Nov 1, 2020
@barpaw barpaw closed this as completed Dec 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@barpaw