-
Notifications
You must be signed in to change notification settings - Fork 493
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
Initialization vector of encrypted files is sent as padded base64 #4172
Comments
Johennes
added a commit
to Johennes/matrix-ios-sdk
that referenced
this issue
Apr 1, 2021
This uses the existing `MXBase64Tools` to trim the `=` padding from the base64 encoded string. The reinsertion of the padding prior to decoding was already implemented (line 224 in the same file). Closes: element-hq/element-ios#4172 Signed-off-by: Johannes Marbach <[email protected]>
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The
iv
value in encrypted files is sent as normal base64 instead of unpadded base64. This breaks other clients which requireiv
to follow the spec precisely.To Reproduce
iv
field and see unexpected==
at the end:Expected behavior
iv
is sent as unpadded base64 as specified in the spec:Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: