-
Notifications
You must be signed in to change notification settings - Fork 63
Raw aes keyrings in a browse not processing zero byte AES-GCM operations. #237
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
Comments
@seebees - Thank you for taking this up. |
Regarding aws#237, the shape of the CryptoKey when dealing with a fallback may slightly differ. By changing all references to AwsEsdkJsCryptoKey I can control any type mismatch.
See: aws#237 Since the WebCrypto decrypt API expects the AES-GCM tag with the encrypted data, zero bytes of encrypted data is not zero bytes of data.
I'm trying to work out the best way to deliver an example. |
Regarding aws#237, the shape of the CryptoKey when dealing with a fallback may slightly differ. By changing all references to AwsEsdkJsCryptoKey I can control any type mismatch.
See: aws#237 Since the WebCrypto decrypt API expects the AES-GCM tag with the encrypted data, zero bytes of encrypted data is not zero bytes of data. fix: Add tests Add tests to specificly cover the Mixed Backend conditions and logic.
Regarding #237, the shape of the CryptoKey when dealing with a fallback may slightly differ. By changing all references to AwsEsdkJsCryptoKey I can control any type mismatch.
See: #237 Since the WebCrypto decrypt API expects the AES-GCM tag with the encrypted data, zero bytes of encrypted data is not zero bytes of data. fix: Add tests Add tests to specificly cover the Mixed Backend conditions and logic.
A few browsers, notably Safari (WebKit), do not properly handle zero byte AES-GCM operations.
In this case a fallback is required.
However for raw AES keyrings the master key is not properly handling this case.
Fix the import and use of the master key.
Add tests.
cc @khadir-syed moving the discussion to here to track the work.
The text was updated successfully, but these errors were encountered: