Re:Microsoft says mandatory password changing is “ancient an...
by gmfawcett on Monday April 19, 2021 @12:50PM
(#26864922)
A user could defeat this by changing to an intermediary password and then incrementing the original. E.g. sign in with current password "cat100", change it to "dog100", then sign in as "dog100" and change to "cat101".
Re:Microsoft says mandatory password changing is “ancient an...
by tshaddox on Monday April 19, 2021 @12:55PM
(#26865003)
The system can just store the last n passwords (salted and hashed, of course) for each user. I seem to recall some software I had to use in college wouldn’t let you toggle between passwords like this.
Re:Microsoft says mandatory password changing is “ancient an...
by michaelt on Monday April 19, 2021 @01:35PM
(#26865620)
Ah, but one could write a script to change password n+1 times.
That's why, to encourage users to assume last month's password was compromised, when my users change their password the old password is automatically posted to twitter
/s
Re:Microsoft says mandatory password changing is “ancient an...
by unrealhoang on Monday April 19, 2021 @01:39PM
(#26865687)
Storing salted & hashed passwords can only prevent reuse the exact old password, it can't prevent reuse & increase though.
Re:Microsoft says mandatory password changing is “ancient an...
by tshaddox on Monday April 19, 2021 @01:56PM
(#26865940)
Unless you generate all the password variations upfront and salt+hash them all! I think I’ve heard that some place (maybe Facebook?) does this for common password entry mistakes like capitalization.
Almost all the implementations require the old password when you change it to the new password, so it's trivial to check if they are too similar.
If you're afraid of sending cleartext passwords - do the too_similar check on the client side. The users that can write their own client to bypass client-side checks are exactly the users you don't need to worry about.