3 ms·
I peaked at some of the stats regarding his brute force attempt, but I couldn't figure out how much progress he was making and whether a bf was actually feasibl
by AdmiralAsshat 7y ago
I peaked at some of the stats regarding his brute force attempt, but I couldn't figure out how much progress he was making and whether a bf was actually feasible with LUKS. Is it something to be concerned about at this stage?
- loeg 7y agoLUKS1 (2004 design) uses PBKDF2 with 2 seconds worth of iterations. It's not especially susceptible to brute force. The only reasons to be concerned are (1) your password is very weak, or (2) you initialized the LUKS volume on an extremely low power or heavily oversubscribed CPU such that 2 seconds of PBKDF2 iterations is below the 2016 NIST recommendation for 10,000 iterations. (The LUKS implementation may/should have an iteration floor that would make this (2) concern invalid, but I'm unfamiliar with the codebase and unable to speak to that.) LUKS2 uses argon2. See, e.g., Cryptographic Right Answers[1]: > Password handling > Percival, 2009: scrypt or PBKDF2. > Ptacek, 2015: In order of preference, use scrypt, bcrypt, and then if nothing else is available PBKDF2. > Latacora, 2018: In order of preference, use scrypt, argon2, bcrypt, and then if nothing else is available PBKDF2. [1]: https://latacora.micro.blog/2018/04/03/cryptographic-right-answers.html https://latacora.micro.blog/2018/04/03/cryptographic-right-a...