4 ms·
As attackers get better, we can just up the ante. More rounds, more memory usage, etc. If you're building software in 2016, you want to use one of the followin
by sarciszewski 11y ago
As attackers get better, we can just up the ante. More rounds, more memory usage, etc.
If you're building software in 2016, you want to use one of the following for turning a password into a crypto key:
- Argon2
- scrypt
- bcrypt
PBKDF2 should be your last resort. Don't fall back to a simple hash function.
- logicallee 11y agothat makes zero sense. something encrypted in 2001 isn't supposed to magically become plaintext in 2016 because "attackers get better." it's fundamentally not the promise of encryption. (I thought.)
- sarciszewski 11y agoUh, no. AES was originally only slated to survive until 2030. Advances in cryptanalysis are hard to predict, but attacks always get better.
- noddingham 11y agoWait what? It feels like you're trying to argue with the results of Moore's law. How does it make zero sense that what would have taken years on 1990s hardware now may only take weeks on 2016 hardware? Why do you think recommended password length and complexity has increased? Why do you think the default for RSA key length is 2048-bit now instead of 1024?