two separate Okta instances. It was a coin toss as to which one you’d need for any given service
oh, and a third internally developed federated login service for other stuff
90 day expiry for all of the above passwords
two different corporate IM systems, again coin toss depending on what team you’re working with
nannyware everywhere. Open Performance Monitor and watch network activity spike anytime you move your mouse or hit a key
an internally developed secure document system used by an international division that we were instructed to never ever use. We were told by IT that it “does something to the PC at a hardware level if you install the reader and open a document” which would cause a PC to be banned from the network until we get it replaced. Sounds hyperbolic, but plausible given the rest of the mess.
required a mobile authenticator app for some of the above services, yet the company expected that us grunts use our personal devices for this purpose.
all of the above and more, yet we were encouraged to use any cloud hosted password manager of our choosing.
IME is even worse than that. It runs on a supervisor processor in the chipset that has privileged access to the memory, peripherals, and CPU, and can run when the rest of the system is powered off. IME is how Intel AMT can serve as a KVM-over-IP, and just because you don’t have a CPU with Vpro doesn’t mean all the components aren’t there for an exploited or backdoored ME firmware to remotely log your console or inject keystrokes.
That’s exactly what they are, but instead of connecting to a VAX at the other end of a modem they talk to a shell attached to a pseudo terminal device on the same machine.
There should be a setting in BIOS for sleep state that lets you choose between “Windows sleep” and “Linux sleep”. I know I have to set that to “Linux sleep” on my P14s gen 2 AMD or it wakes up immediately after going to sleep. Updating BIOS and the other firmwares might help too.
However I have a gen 7 from work running Windows that often fails to wake up from sleep or hibernation, and I have to resort to poking the reset button to get it to respond. Coworkers report similar troubles so I think it may be a cursed model.
That said, I’m running OpenSuSE Tumbleweed KDE on my P14s and an X1 gen 5. Everything works smooth out if the box on both machines except for the fingerprint sensor on the gen 5 which doesn’t have mainline fprintd support in any distro.