You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
bain3
changed the title
Change IV generation
Change IV generation to match NIST spec
Jan 28, 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.
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: