-
Notifications
You must be signed in to change notification settings - Fork 268
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
Valid 4S keys are ignored #2932
Comments
ruma/ruma#1719 is my attempt at a first step here. |
Great, thanks! Now that your PR on Ruma has been merge, do you need help to update the SDK? |
Help would be appreciated, but I'll probably get to it eventually if you're busy. |
This patch updates Ruma to the latest commit on its `main` branch. This is useful for matrix-org#2932.
I've updated Ruma to its latest commit on |
This patch updates Ruma to the latest commit on its `main` branch. This is useful for matrix-org#2932.
Thanks! I think this is probably fixed by #3046, but we'd better test it to be sure. |
#3048 adds a test, so I'm reasonably happy this is now fixed. |
Per element-hq/element-web#26721, Element-Web R does not include the
iv
andmac
properties onm.secret_storage.key.[key_id]
account data objects. This causes Element X to ignore the key with:UnsupportedAlgorithm("m.secret_storage.v1.aes-hmac-sha2")
.However, these properties are (and always have been) optional. The spec was recently clarified to say that, where they were missing, clients have to assume the key is valid.
The text was updated successfully, but these errors were encountered: