You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The iv value in encrypted files is sent as normal base64 instead of unpadded base64. This breaks other clients which require iv to follow the spec precisely.
To Reproduce
Send an image with Element iOS in an encrypted room.
View the (decrypted) event source, find the iv field and see unexpected == at the end:
Expected behavior iv is sent as unpadded base64 as specified in the spec:
The 128-bit unique counter block used by AES-CTR, encoded as unpadded base64.
Smartphone (please complete the following information):
Device: 8+
OS: 14.4.2
Version: 1.2.7
The text was updated successfully, but these errors were encountered:
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 <n0-0ne+github@mailbox.org>
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: