-
Notifications
You must be signed in to change notification settings - Fork 154
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
aes-gcm-siv: outdated aes and cipher #410
Comments
Will get to this soon. Recently updated |
I began an attempt at this and encountered a problem: Once that's fixed, my branch here should be mergeable. You can see where it fails now by |
@rozbb I've already done |
It doesn’t look like aes-gcm does interleaved/parallel decryption, whereas aes-gcm-siv currently does. Is that right?
… On Apr 26, 2022, at 17:43, Tony Arcieri ***@***.***> wrote:
@rozbb I've already done aes-gcm. It's a fairly straightforward upgrade
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
You're right, that is different |
See above PR. I have a branch that successfully updates the dependencies of |
We're trying to bring the AES version up so we can do CBC (required for FIDO2) but unfortunately the aes-gcm-siv crate is locked to an outdated version of AES, and this is blocking on a type that is missing in the `block-ciphers` crate. For now, we're using a patched version of aes-gcm-siv from rozbb's repo, which allows us to move forward, but this needs to be reverted once a new version of the official crate is patched.
We're trying to bring the AES version up so we can do CBC (required for FIDO2) but unfortunately the aes-gcm-siv crate is locked to an outdated version of AES, and this is blocking on a type that is missing in the `block-ciphers` crate. For now, we're using a patched version of aes-gcm-siv from rozbb's repo, which allows us to move forward, but this needs to be reverted once a new version of the official crate is patched.
it seems fixed in 0.11 #464 |
good to bump the crate versions (as in #409 for aes-gcm)
The text was updated successfully, but these errors were encountered: