1.26.29 Issues with Custom PIM & Changing the KDF
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
@idrassi
1.26.29 does not allow the user to correct the custom PIM value.
Passwords in my tests are 20 characters.
You get a warning box that the PIM value is larger than VeraCrypt default with only an OK button.
Clicking the warning OK button merely proceeds with the KDF change using the too large/small custom PIM value with no ability to abort the operation.
See my post below for all the details in the 1.26.27 Beta thread.
https://sourceforge.net/p/veracrypt/discussion/general/thread/90471499cb/?page=1#9223
Last edit: Enigma2Illusion 19 hours ago
Same problem exists with using less than 20 character password as long as the original KDF custom PIM is larger than the default new KDF PIM value using the carryover of the original KDF custom PIM being used for the new KDF custom PIM.
Last edit: Enigma2Illusion 19 hours ago
Thank you for bringing this up. I completely missed you analysis for 1.26.27 Beta, this is no good :-(
I'm working on a fix because this issue can cause really problems for users.
The introduction of Argon2 had many side effects that I discover little by little. That's why I added the Cancel button the waiting dialog because entering wrong password by accident with custom PIM that is large in autodetection mode caused very long waiting time driven by Argon2.