4 ms·
What about the "oops we accidentally logged passwords in plain text" issue mentioned in the article?
by gok 8y ago
What about the "oops we accidentally logged passwords in plain text" issue mentioned in the article?
- tptacek 8y agoI don't believe that's a security concern that motivates entire new protocols; further, I think it's one of those security issues that is talked about more than it is actually felt. So far as I know, none of the HIBP datasets have come from logs? I'd be interested in corrections. The "real" issue PAKEs address is long-term compromise, where an attacker can observe passwords out of memory. For that matter: for attackers to get log files in the first place, 9 times out of 10 they had to get RCE somewhere in prod, and that is already game over. And, there's a lot of things you'd do first do address game-over than replacing your TLS login POST with a PAKE handshake.
- gok 8y agoI mean as mentioned in the article, it happened at Twitter. And what about Heartbleed-style issues?
- tptacek 8y agoIt happened at Twitter, was discovered internally at Twitter, remediated at Twitter, and disclosed by Twitter. It was talked about but not in any apparent way felt. And, again, if that's your only concern, there are simpler ways to mitigate that threat than a whole PAKE. PAKEs don't address Heartbleed-like issues; in fact, they create more opportunities for them.