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
Debian release version 1.16 seems to error out if there is not enough memory available to decrypt a file. From what I understand, it should be possible to do the decryption, albeit slower.
The text was updated successfully, but these errors were encountered:
It is theoretically possible to use less memory and more CPU time, but I haven't written the code necessary to implement this. If anyone is interested in working on this, please contact me to discuss how this would be done before you start writing code.
I'd be interested in giving this a shot @cperciva. Let me know whatever I should be aware of before I get started. Email is on my github profile, if you prefer that.
@DavidBurkett Great! Not too much to be aware of; in step 3 of smix you want to record some of the X values into V[] rather than all, and in step 8 you want to look up the closest preceding V[] value and then iterate blockmix_salsa8 on it some number of times.
I'd suggest making this an explicit command-line option to the scrypt utility rather than turning it on automatically based on the available memory -- the available-memory estimator isn't very accurate so there will likely be times when people want to use -f rather than --low-memory.
Debian release version 1.16 seems to error out if there is not enough memory available to decrypt a file. From what I understand, it should be possible to do the decryption, albeit slower.
The text was updated successfully, but these errors were encountered: