3 ms·
No, it's more like "attacker gets the range, sends it to the API, gets all the possible hashes from the API, tries the corresponding plaintext passwords, thus n
by StavrosK 9y ago
No, it's more like "attacker gets the range, sends it to the API, gets all the possible hashes from the API, tries the corresponding plaintext passwords, thus needs only ~200 tries instead of X million".
Granted, your password was compromised already if it was in that list, so it needs to be changed anyway, but there's some information revealed by the hash (of course, how else could it be checked?).
- jgrahamc 9y agoGot it. That makes sense.
- dingo_bat 9y agoBut the whole point of the api is that you don't use the password if it is found in the list. So the attacker will know about the 200 strings that are definitely not the password.
- StavrosK 9y agoAssuming you managed to instantly change the password on every single service you've used it, yes.
- euroclydon 9y agoNobody is talking about it, but to compromise someone, you also need the username, which is not sent.
- StavrosK 9y agoAh, that's true. In any case, I don't think this is really a reasonable vector of attack, I was just being pedantic at jgc's "the password is not sent" comment.