4 ms·
Both the site and the blog post are devoid of good information, like an explanation of the exact design issues in the affected protocols where this effect occur
by niftich 10y ago
Both the site and the blog post are devoid of good information, like an explanation of the exact design issues in the affected protocols where this effect occurs. I would've liked to see that.
In either case, TLS does this too [1], so the mitigations they recommend will have no effect. Worth reading cryptographer Thomas Pornin's opinion of the matter [2] in response to that thread.
[1] https://security.stackexchange.com/questions/109973/ https://security.stackexchange.com/questions/109973/
[2] https://security.stackexchange.com/a/109976 https://security.stackexchange.com/a/109976
- userbinator 10y agoI'll quote the last sentence of his post since I think it's the strongest argument to why this is not a particularly interesting security issue: A realistic answer would be to point out that if leaking the password length allows breaking it, then this is a poor password to begin with, and you should probably fix that. (Aside: I wonder how many systems have censored Pornin's last name.)
- deleted 10y ago[deleted]