Just check in the top desk drawer for the sticky note with the passwords written on it - that’s what I would do if I were a thief.
If I ran into those rules, I would be completely stumped - you have to generate a random, nonsense string, and you can’t write it down? Fuck that shit indeed! I can generate a random string, or I can remember a password - I can’t do both.
We demanded that management include a time category for ‘completing time reporting’, and then we charged time to that category. (Actual time, we didn’t pad it.) But still, seeing the totals from all the programmers to that category got some results. Management had to take notice of the amount of time being wasted here. Some department managers responded by forbidding use of this category, or limiting the amount of time their workers could report to it. But enough leaked through to higher management that they eventually took action to streamline the reporting.
Or install one of the programs that simulate a keystroke when the keyboard has been inactive for a specified time period. (I used such a routine in 1974 on our IBM 370/168 mainframe.) Now they are usually run from flash drives. Can be found online, usually free.
Installing a program that hasn’t been approved by the very people that set up the system that causes your head to bang against the wall, that isn’t going to be allowed either.
I’d be highly surprised if an IT department that requires such draconian password rules were to leave users with the privileges they would need to install such a utility.
And, obviously, such automated keypress programs are written so they do not have to be ‘installed’ to work. They run as an application program, right from local media. I think there was even one that ran as a keyboard macro within the 3278 dumb terminal itself – never even ‘ran’ on the processor itself at all.