No, that's not a good password.
I spent last week looking at security of passwords and found users circumventing the requirements. These are some of the developers with DB access, let's begin with the core developers:
Superadmin (access to prod dbs) now changed passwords: dbadmin, dbms, admin, p4sswordfordb
Web Passwords (old now) : web ecomadmin store Hi123
And finally... We arrive. Old LDAP passwords: Fuckyou123 Fuckthisshit1235 ldap password32141 Smith215 windows10
How the fuck did these people circumvent the policy? Oh I'll tell you how! The old sysadmin gave His fucking credentials to everyone because he was "too busy" to reset passwords. (spoiler: was fired for not doing anytbing to help anyone)
Fuck sakes. Why just fucking why.
Posted Jul 15, 2019, 11:55 PM UTC
Upper case, lower case, numeric. This smells of "password composition requirements policy", and users being trained in exactly the way you'd expect to deal with it.
Also 16 characters. I'd say this is a pretty decent password compared to the usual (like "qwerty" or "12345")
At a guess it only failed to work due to "fuckthisshit" probably be treated as a discrete word in a brute force attack database (or some variation). Dumbhorsetail1235 would probably be uncrackable in comparison.
Well, at least according to https://haveibeenpwned.com your guess is spot-on
Password complexity requirements: yeah, fuck that shit
Passwordcomplexityrequirementsyeah1!
Doesn't anyone add spaces to their passwords?
I'm from the DOS generation. Spaces give me hives.
My bank limits password's max length to 16 characters. So no budget for spaces.
I reset one of my passwords whilst doing an internal demo the other day. It said Password1 was a strong password...
It has 3 of the 4 character categories though.
It does but it shows both how arbitrary they are how misleading they can be to end users.