The answer as always is, it depends.
Not all implementations rely on shim.
if you set up secureboot without doing anything more than instaling the OS… yeah probably it is true. Edit: e.g. GRUB2 generally relies on shim. sysemd-boot doesn’t
I haven’t checked the specific key that signs shim to confirm the expiration date, but there generally is a date, as we’re talking about certs and keys here.
Edit 2: Basically what this article is saying is that the machines will need a new platform key (mited in 2023) enrolled in the tpms, with often comes from the firmware (when tpms are wiped for initial enrollment of a new install/setup, they tend to enroll whatever platform keys from microsoft are baked in to the uefi firmware).
So basically, if you haven’t had a bios/uefi firmware update since 2022, there’s no way for you to have have the new key trusted by your tpm, and the whole chain of trust falls apart when the key you do have expires. So you’ll need to disable secureboot. If you use shim and/or the microsoft platform key in someway.
I’m on hyperland, and I’ve configured ydotool to do some of this work. It can move the mouse, enter keyboard shortcuts and do a bunch of things that autohotkey can, however it is by no means a complete solution, or one that comes with sensible defaults. It’s just a daemon and client, and you’ll need to set it up to do what you want.
As far as I know there’s no record and replay function, though you could likely script one.
Also, for triggering the scripts, you’ll need to set your Desktop’s keybindings to point to them.
For me, it filled the requirements that it was launchable by systemd unit, as the user on login.
I use it for a vairiety of tasks, but the primary one is typing out my clipboard as if I had pasted something. I rebound alt + shift + p to that, so I can paste windows login passwords or whatever in to Teamviewer/other stuff that doesn’t accept a paste command.