* Your password must be between 7 and 20 characters
* Your password must contain
* At least one number
* At least one upper-case letter
* At least one symbol from this list (!@#$%*)
* Your password must be changed every 30 days
Plus this: https://blog.mamota.net/resources/img/wat_2.gifA system I use not only has that requirement (along with a very insane set of requirements like "no patterns like 123 or ABC"), but they also NEVER let you reuse a password.
Which means they have a database of every password I've ever used on a machine somewhere, hashed or otherwise.
So the annoying workaround is to append year+month on the end of each password (which I was basically told to do when first setting up my account). So combined with a "maximum 10 characters" leaves 6 for my actual password...
Or do <password>, <password>1, <password>2, ...
(╯°□°)╯︵ ┻━┻
I don't know how people who don't use password managers are able to deal with this kind of crap at all.
I do use a password manager however, so I don’t really notice.
┬─┬ノ(º_ºノ) calm down, take it easy.
they do not deal with it, they reuse passwords increasing the degree if the problemI don't think so... So are your old passwords stored in plain text somewhere so they can compare ?
Scary...
Yes, maybe: https://en.wikipedia.org/wiki/Locality-preserving_hashing
> So are your old passwords stored in plain text somewhere so they can compare?
You betcha!
But I would guess they use plain text :-(
Previous Password:
New Password:
Confirm New Password:
They don't need to store the plaintext password, as you're giving the old password plaintext to them in the same dialog. Now, if such rules were against "any of your last 4 passwords" instead of just the last password, then that's much more difficult to do. (Obviously nobody is going to cooperate with a form requiring the person to submit their last 4 passwords as part of the password change dialog.)Or did I misunderstand you?
But now that Im writing it out, I was clearly wrong anyways
I thinking something along the lines of taking every substring of 4 characters, and then for all permutations of those 4-tuples, plug it back into the string hash and store. Assuming the goal is to not share any 4-substring with the new string
So I think (N-4) + 1 gives you the number of 4-character windows
4! for the number of permutations of that 4-char window
So 4!*(n-3) total hashes
Which I guess is actually the same work you'd have to do anyways if you stored the plaintext; just without storing each variant
- password must be between 7 and 8 characters long
- has to include one number
- has to include one of the following: $#!*, no other special characters are allowed
It was so horrendously bad it's not even funny.
The NHS online booking system my GP uses has rules like this. Pretty much guaranteed to prevent old people from being able to login.
How do you enter a fractional character?
Algorithms have their downside, sure, but for someone like me who is often working on other computers that aren't mine, managers are a non starter.
You can even use something like InputStick to auto-type the password into the other computer if you'd rather not do it manually.
Copying over a really long generated password is much harder than an algo you can perform in your head.
For the couple passwords I have to enter on other devices (like Netflix) I often just create them by hand, and choose something easy to type on an on-screen keyboard, and then store it in my password manager. For example: "assdeeeerffghhhjuiop". If the keyboard is sorted alphabetically instead of QWERTY, I'll adapt to that.
I generally only have to type this in once or twice a year so it's not a huge deal.
I would recommend you to use any password, but rotate the credentials every time you enter them in one of these.
It's free, fast and secure. Try ANPM:
Do note that you don't need anything more than 22 random mixed-case letters & digits: 26 lower-case letters plus 26 upper-case letters plus ten digits is 62, and 62²² ≈ 2¹²⁸.
Completely agree re. the ineptitude of the developers of sites that try to limit one to less than that.
It is awful for actual third-party passwords.
Here's a direct link: https://www.eff.org/files/2016/07/18/eff_large_wordlist.txt
Of course passwords would be case sensitive, why wouldn't they be?
This is one of the big problems with an algorithm. You'll eventually come across a site that -- for whatever reason -- doesn't allow that particular special character (or has a length restriction, or something else that makes your algorithm break). Now what do you do?
I use a password manager and generate 30-ish character long passwords, and I still occasionally run into sites that tell me it's too long. No big deal, I just generate one at the max length they support, save it, and move on. It literally makes no difference to me, other than I scoff at the ineptitude of the people that built the site and have to click a couple more times to get a new shorter password.