3 ms·
Slow security is bad for many reasons: 1) It means default-secure will not happen. If the NSA has to spend 10x as long to attack your security, but 1/10th as
by aidenn0 9y ago
Slow security is bad for many reasons:
1) It means default-secure will not happen. If the NSA has to spend 10x as long to attack your security, but 1/10th as much communication is encrypted, it's a win for them (since now the simple fact that something is encrypted means someone put effort into it, which is a good signal that it will be useful).
2) Brute force attacks are typically embarrassingly parallel, and can be amenable to special purpose hardware (e.g. GPUs). An attacker with an 8 GPU system spend $10k and can attack PBKDF2 much faster than a $10k server will be authenticating people.
3) If your security relies on slowness, then people will pick less-secure defaults. If you can get an equivalent level of security per cpu-cycle, then people will pick a higher security margin (this is the non-binary version of #1).
3DES is way slower than most crypto primitives used today. I haven't seen it recommended much though.