Viy$Ehi8sy3&2WQpasswords when you enforce changing them regularly:
password01!? password02!? password03!? password04!? password05!?Viy$Ehi8sy3&2WQpassword01!? password02!? password03!? password04!? password05!?@halotroop2288 "IF" meant as in if.
#NTLM is a weak hash function used by #Microsoft #Windows which is trivial to crack, as even almost two decades ago sites like #CloudCracker offered to brute-force it for U$D100...
#MandatoryPasswordChangePolicies are like #DaylightSavingsTime:
- Proven to be harmful
- Proven to be counterproductive
- Don't add any value
- Demand addition unpaid labour
- Are unpopular
- Don't do anything beneficial for anyone
@halotroop2288 Will do so when full-text search actually works. ^^
No seriously, If #FullTextSearch were to actually work then noone would've needed to use Hashtags anyway...
@starshine Upper + lower + number + punctuation + length 12? Hmm, "Fri-03-Nov-2023" fits that and now I don't need a password manager, just a calendar...
..is a thought I've had.
No, no, no.
It is of course:
password!&01
password!&02
password!&03
password!&04
only ever change the last letters, never letters, where you have to navigate to.
pwgen -y 12 1@starshine There's a reason NIST says that regular password changes should be avoided.
But what does NIST know... 😂🙈
@starshine Reply guys going out of their way to discuss how your observation (which is true) is not a problem with their choice of Zod's own password manager.
I wonder how they use their god given tools on the login screen of their operating system 🤭
No, wait! I don't want to provoke more replyguyism 😬
#65*B9dXdSay5$zn #6i34SzLoZJdT&Fz Flavorful-Capillary-County-Squint-Translate-Resubmit-Underpass-Apache-Smartly8-Kinfolk-Crunching-Lifting@starshine we have "cyber insurance" that makes us make our users change their passwords every 45 days.
We've told them that we don't want to do that, for this very reason and they told the business manager it would effect the premium.
So true!
And frequency of change doesn't really matter...
@starshine my first ever malicious compliance at work was at a company that had the following password policy codified in its official procedures:
Your password must meet complexity and length requirements X, Y, and Z.
You must change your password each month.
You must not use a form of incremental passwords.
You must not write your password down or in any way store it.
@starshine We were a small company so the person responsible for the policy was the sole IT employee and he was adamant that it was a good policy.
Each morning, without fail, I would call him up and have him reset my password because I'd forgotten it.
It became quite a battle of stubbornness.
I saw that so many times when I was working. Colleagues would use a single word then add two digits for the current month of usage. And even then, there'd be a post-it note somewhere close by. Or the last page of the work diary was another favourite place.
@starshine based password behaviour is rotating through a different anime every time you have to change
...That was at my old work, though; at my current one I just change one number at the end
@starshine @somcak this is so real, NIST even recommends against it
@starshine I'm not sure how many people choose to use the first kind of password. That's why encouraging passwords like "Horse+Battery+Staple" is a good idea.
Enforcing frequent password changes is widely regarded as a dumb idea. Except for dumb auditors.

Il y’a 16 ans, j’écrivais
https://ploum.net/177-le-gilet-de-sauvetage-et-le-tgv/index.html
(pitin, je suis vieux)