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

[question] AES GCM — iv length #74

Open
nichoth opened this issue Aug 8, 2024 · 1 comment
Open

[question] AES GCM — iv length #74

nichoth opened this issue Aug 8, 2024 · 1 comment

Comments

@nichoth
Copy link

nichoth commented Aug 8, 2024

It looks like the iv length is defaulting to 16 bytes

From this discussion, it seems 12 bytes is preferable.

Thoughts about this?

@matheus23
Copy link
Member

matheus23 commented Aug 9, 2024

Yes. It's better to have an iv length of 12 with AES-GCM.
This library has a bunch of suboptimal defaults - e.g. around utf8 vs. utf16 encoding, too, or having AES-CTR instead of AES-GCM as default.
We moved away from it during the time at fission and spent effort on the rust parts instead (so mostly rs-wnfs).

If one wanted a good library like this today, I'd recommend just going with uint8arrays, localforage + the WebCrypto API directly.

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