Skip to content
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

Don't limit the IV to 16 bytes #40

Closed
Syndace opened this issue Nov 18, 2018 · 7 comments
Closed

Don't limit the IV to 16 bytes #40

Syndace opened this issue Nov 18, 2018 · 7 comments

Comments

@Syndace
Copy link

Syndace commented Nov 18, 2018

The recommendation for the IV of AES-GCM is 12 bytes. By limiting it to 16 bytes you break compatibility to clients following the spec.

@Syndace Syndace changed the title Don Don't limit the IV to 16 bytes Nov 18, 2018
@Neustradamus
Copy link

Neustradamus commented Feb 17, 2020

A little change in 2 other branches (not master):

Feb 16, 2020

  • Accept 12 byte IVs

Linked to:

@Syndace
Copy link
Author

Syndace commented Feb 23, 2020

@chrisballinger looks like you fixed this in the two non-master branches, thanks! Feel free to close this now.

@Neustradamus
Copy link

@Syndace: Not in master... Master is important...

@Neustradamus
Copy link

@chrisballinger: It is good?
Dino 0.2.0 has now "good" OMEMO.

@Neustradamus
Copy link

@chrisballinger: Any news?

@Syndace
Copy link
Author

Syndace commented Nov 29, 2023

I think this has been fixed on master since ce0ddbf

Thanks!

@Syndace Syndace closed this as completed Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants