-
Notifications
You must be signed in to change notification settings - Fork 2
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
Change IV generation to match NIST spec #9
Comments
This is a breaking change and would require to have to keep the old scheme for a while for backwards compatibility. |
hi, when will" encrypt(upload) & decrypt(download) be parallel" feature be available? |
I'm not sure. It is just a new possibility that opens up. I think it will first be implemented in the native client because I feel it could get more use there, since it will probably be run on servers and desktops. Right now it is not an important feature. |
Currently IVs are encrypted with the file for redundant security. According to the NIST Special Publication 800-38D they do not need to be secret, and only require to be unique, not cryptographically random. This could allow blocks to be decrypted and handled in parallel.
The text was updated successfully, but these errors were encountered: