3 ms·
High point: Recommending encrypt then mac. Still an issue today. Low point: Saying MD5 is too slow. We have the opposite problem today.
by tedunangst 16y ago
High point: Recommending encrypt then mac. Still an issue today.
Low point: Saying MD5 is too slow. We have the opposite problem today.
- tptacek 16y agoIn what sense do you mean that? That MD5 is breakable or that hash functions are generally too fast?
- sdrinf 16y agoBoth actually: Time-based attacks exploiting the fact that we have fast networks, and rainbow/brute-force attacks exploiting CPU speed.
- tptacek 16y agoIt is not a flaw in new hashing algorithms that they run fast. Running fast is their design goal. Timing attacks don't exploit properties of hash algorithms; in fact, they would prefer compute to be slower (and networks to be faster).
- tedunangst 16y agoThat it runs too fast now. I've not heard many complaints about hash functions being too slow recently. It stood out as a not particularly sage comment (to somebody with the benefit of hindsight).
- tptacek 16y agoThat's not a problem we have with hash functions; it's a problem we have with naive password storage schemes.