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

Change IV generation to match NIST spec #9

Open
bain3 opened this issue Jan 28, 2022 · 3 comments
Open

Change IV generation to match NIST spec #9

bain3 opened this issue Jan 28, 2022 · 3 comments

Comments

@bain3
Copy link
Owner

bain3 commented Jan 28, 2022

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.

@bain3 bain3 changed the title Change IV generation Change IV generation to match NIST spec Jan 28, 2022
@bain3
Copy link
Owner Author

bain3 commented Jan 28, 2022

This is a breaking change and would require to have to keep the old scheme for a while for backwards compatibility.

@practicingman
Copy link

hi, when will" encrypt(upload) & decrypt(download) be parallel" feature be available?

@bain3
Copy link
Owner Author

bain3 commented Apr 7, 2022

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.

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