The joy of repetition really is in you
The other day, I was trying to sign into my Subway loyalty app. That's Subway the sandwich shop. They've changed their security model, and please would I pick a new password.
I have a generic password that I use for everything I don't really care about. It's a decent enough password (the sort of sites that tell you how strong your choice is usually put it at medium).
Subway rejected it: it had no capital letters. I tried a different one, which was rejected due to having no numbers. Ok, fine. I'll stick a capital in my generic password, and I'll doubtless forget I've done that and have to reset it in the future, but really who cares.
Subway rejected it because it had consecutive repeated characters. Wait, what? Does that rule actually achieve anything other than massively reducing the search space a potential hacker needs to hit?
To be honest, this is my feeling about all the "must have a capital", "must have a numerical digit" rule. It's quite possible to produce a strong password with neither. By enforcing these, you're just making my password very slightly easier to brute force.
Of course, given the general approach to passwords (see Ashley Madison's list of cracked passwords) I appreciate that the rules are there for a reason.
But "no repeated letters"? I don't get it.
no subject
It's the Sparks one with the monkey, over and over and over and over.
(no subject)
(no subject)
no subject
They also asked me to type in my "phoning up" password (I was on the phone with them at the time and did check, this was correct!) and it kept rejecting. Because the guy on the phone repeatedly neglected to mention that their system had recorded it in ALLCAPS and run all the components of it together so instead of Word NUMBER Word I had to enter WORDNUMBERWORD. Which makes sense - except that when I set it up originally they said the spaces were fine, and it would strike me as the kind of thing that is rather important to tell the customer if you're trying to fix a major problem by getting them to do this.
no subject
I have a petty password (with variants for annoying companies) which I put in a wiki page (protected by stronger password). Most of it is 32 years old, the end bit only 25 years old
I have a stronger password which is a decade old
I have individual passwords for the real money, written with gaps on a piece of paper on my desk.
(no subject)
(no subject)
no subject
There's also the fun problem when passwords are required to have or not have non-alphanumeric characters. And of course which characters fall in to which the three groups (must not use, may use, must use at least N of) is massively variable.
And don't get me started on password recovery questions.
This sort of malarkey is why I gave up my old password system for a password manager. It's great. So much better for practical convenience, and also (probably) more secure. It turns out I was using my old system for ~200 passwords. Now I have >300, but it's waaaay less bother and mental effort. I don't need to worry about signing up for a new account somewhere - it's easy.
(no subject)
(no subject)
(no subject)
(no subject)
(no subject)
no subject
(no subject)
no subject
no subject
(no subject)
(no subject)
(no subject)