Back in the DOS and Windows 3.1 days, they tried to lock it down with whatever software they had. We found a way around it. Even the DOS based menu system, we managed to copy the menu software out with its configuration file. Then we experimented with the “encrypted” password in the configuration file and found out that if we removed it, the system would allow you to do anything but that also meant we could create our own password and look at the “encrypted” password. We quickly found out that it was just shifting the ASCII table. We then “decrypted” the school password. Such 12 your old hackers 😆

I was just to clarify that you’re not sitting with software full of security issues because of older versions of packages. And then some bonus info on what “stable” means in Debian :-)

Old but not necessarily out of date. The system is at a stable state. It’s working and we don’t want to make changes that can compromise stability. New features and other big code changes comes with increased risk of something breaking. Debian Stable means running code that have been tested and used a lot.

Security fixes and critical bugs get back ported if feasible, or a package might get updated to a newer version.

Encryption is not a panacea, because if someone ever forgets their password (something common for the layperson), the data on that drive is inaccessible.

It’s because of stuff like this that Microsoft wants people to create an Microsoft account. Recovery key automatically saved to your Microsoft account. For business the recovery key can also be automatically saved in a central location.

Any respectable company with Windows would be using BitLocker - full disk encryption. It’s super easy to setup if your computer has TPM, fully transparent for the user in most cases.

SuSE destroy collaborators like OL, CNC and probably Turbo

I’m very new with this and have no idea what OL, CNC and Turbo are. Could you please elaborate?