I think I’m confused on your point.

I interpreted your statement to mean “adding a requirement for certain types of characters will decrease the number of possible passwords compared to no requirements at all”, which is false. Even in your example above, with only two letters, no numbers / special characters allowed, requiring a capital letter decreases the possibilities back to the original 676 possible passwords - not less.

Perhaps you’re trying to say that passwords should all require certain complexity, but without broadcasting the password requirements publicly? I suppose that’s a valid point, but I don’t think the tradeoff of time required to make that secure is worth the literal .000001% (I think I did the math right) improvement in security.

Edit: also, password prompts don’t tell you which characters you got right, so really you can only eliminate passwords which only have lowercase or only have uppercase letters, so you’d reduce possible passwords to 676 + 676 = 1352 (lowercase first letter & uppercase second letter + uppercase first letter & lowercase second letter). This is still more passwords to crack than no requirements at all.

I just can’t math out any examples where providing requirements decreases security, no matter how short & simple the password is. The only thing I can think of is requiring specific characters in a specific spot, which is entirely unheard of in practice.

At one point, Charles Schwab allowed a password of infinite length, but SILENTLY TRUNCATED ALL PASSWORDS TO 8 DIGITS.

This is something I sent a few angry emails about wherever I could find an opportunity.

Provably false. That’s only true if the rules specify some really wacky requirements which I haven’t seen anywhere except in that one game about making a password.

Think about it this way. If you have a password of maximum length two which only accepts lowercase letters, you have 26 choices for the first character & 26 for the next. Each of the 26 characters in the first spot can be combined with any of the 26 characters in the second spot, so 26 * 26 = 676 possible passwords.

By adding uppercase letters (for a total of 52 characters to choose from), you get 52 * 52 = 2704 possible passwords. It increases significantly if you increase the length beyond two or can have more than just upper & lowercase letters.

Computers have gotten so efficient at generating & validating passwords that you can try tens of thousands of passwords in a minute, exhausting every possible two-letter password in seconds starting with aa and ending with ZZ.

The only way you would decrease the number of possible passwords is if you specified that the character in a particular spot had to be uppercase, but I’ve never seen a password picker say “your fourth character must be a lowercase letter”.

I agree - I do use passphrases in some critical cases which I don’t want to store in a password manager.

However, I believe passphrases are theoretically more susceptible to sophisticated dictionary type attacks, but you can easily mitigate it by using some less-common 1337speak character replacements.

Highly recommend a password manager though - it’s much easier to remember one or two complex master keyring passwords & the random generated passwords will easily satisfy any application’s complexity requirements.

Erm I might be showing my inexperience here.

Is there no equivalent to man LOAD in the commodore world? Or even just help?

That’s the ticket, IMO. I start off assuming they know, then pause to ask “are you familiar with x concept?”

If they say yes and they really mean no, there’s really not a lot I can do. But it seems to make people feel at ease when talking to me - I don’t get called out for over explaining or infantalizing people this way.