this post was submitted on 27 Jul 2023
1466 points (98.2% liked)

Memes

45586 readers
1523 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] psilocybin@discuss.tchncs.de 7 points 1 year ago (2 children)

That's the point though.

You're not supposed to have the old password. If you had the old password you could just compare it to the new password.

The only way you can do it is to take the new password and make a hash for every possible single-character variation and compare them all to the old hash

[–] Reliant1087@lemmy.world 1 points 1 year ago

Sorry, that's what I meant as well :) Came out upside down when I wrote. We used to figure out shitty ISP router passwords this way by having a table of common passwords and their hashes.

[–] abraxas@lemmy.ml 1 points 1 year ago (1 children)

They shouldn't be storing the old password hashed, either. Expired password hashes should be destroyed like any other potentially-sensitive information that is no longer business critical.

There is a reason hackers look to get users tables even though the passwords are hashed. Because with enough of them and enough time, they can usually figure out plaintext. Giving them 10 previous hashed passwords for each user is just increasing the hypothetical risk.

[–] psilocybin@discuss.tchncs.de 2 points 1 year ago

You're right ofc if you wanted to make a general remark, but wrong if you thought that was what I was implying. Never store hash histories, kids!