Windows 11: This is terrible, really bad, and consumers will be the real victims
Posted: Thu May 12, 2022 7:42 pm
A link below is the video, but I'll give the highlights.
Supposedly, we own and control our computers. Or rather, we used to. Windows 11 will require special features that will stifle competition and give Microsoft near total control of your computer. And it's completely unnecessary, and detrimental to customers and competitors to Microsoft. Here's why.
Windows 11 has two requirements that are not really going to protect people from malware or rootkits; no hardware or software is so bulletproof that it's impervious to attack, These requirements are that the motherboard have Trusted Platform Module (TPM) 2.0, and a UEFI partition table, with "secure boot" turned on. Supposedly this is to ensure that the bootloader of your operating system has not been compromised. Its real purpose is to ensure Microsoft has an unbreakable hold on people's systems and their data, and lock-out competing operating systems and third-party self-booting rescue, repair and recovery programs.
First, this excludes older computers that use older BIOSes since manufacturers have only had it since 2009, and some people are using computers older than this. That's only a minor issue. A bigger issue in the mandate that secure boot be turned on, and TPM installed, to even use the system at all.
What is Secure Boot? Ostensibly, it allows you to know that your operating system was not "hacked," i.e. compromised. The bootloader, which is software on the disk that runs after the machine startup, to load the operating system, must be digitally signed with an electronic key, stored in the firmware of the computer. The firmware on every computer has only the key for Microsoft Windows, and no other operating system. They do not support any other system on PCs. Granted, for the vast majority of people who won't run anything else, that's not an issue. Right now, people who want to run Linux (or BSD, or any other operating system) can turn secure boot off. Now, it is possible you could boot Linux with secure boot off, then push the keys into the TPM. The reason it's possible is that Microsoft signed a secondary key for a Linux bootloader to use.
This means that users wanting to run Linux on the computer they own have to have Microsoft's permission. This also applies for anything else they might want to run. There are many diagnostic, repair, and recovery tools, that, by their nature, are booted instead of an operating system, and do not use Linux. Is Microsoft willing to sign the boot loader every time a toolmaker releases a new binary?
Small developers, open source, and free software developers should not have to get Microsoft to sign the software they create, for you to be able to run it on the computer you own. Now that's one thing. Another is the Trusted Platform Module. It's used to store security keys. Or security information. Windows 10 Credential Manager will store your credentials in the TPM if it's on the computer, instead of on disk.
But, here is the problem; with TPM turned on, and secure boot enabled, Windows will use the Bitlocker software - turned on by default - to encrypt the hard drive. This means the data is scrambled, making it impossible for Linux or third-party diagnostic tools to have access to your data. Where is the encryption key stored? In the TPM, of course. What happens if something goes wrong with the hardware? Right, your data is scrambled, and effectively lost, because it's encrypted, nothing else can access it. Now, it is possible to try to do BitLocker recovery, because they may have stored a backup copy of the password. But where? In the Microsoft account, you're forced to sign up for when you get a Windows PC that's connected to the Internet, whether or not you want one. You are forced to authenticate to Microsoft to be able to access your data on your computer. Another way Microsoft wants to have control over you.
Supposedly, the Trusted Platform Module is to allow the user to trust the software is authentic. But it's worse than that. It's so that Microsoft and other large software companies, and hardware manufacturers, to trust that your computer will do what they want, even if it is against your wishes, even though it is your computer that you own.
With secure boot and TPM enabled, you can no longer do what you want with your computer; Microsoft has total control over what is allowed.
There's much more, and I think it's worth watching.
https://youtu.be/LcafzHL8iBQ
Supposedly, we own and control our computers. Or rather, we used to. Windows 11 will require special features that will stifle competition and give Microsoft near total control of your computer. And it's completely unnecessary, and detrimental to customers and competitors to Microsoft. Here's why.
Windows 11 has two requirements that are not really going to protect people from malware or rootkits; no hardware or software is so bulletproof that it's impervious to attack, These requirements are that the motherboard have Trusted Platform Module (TPM) 2.0, and a UEFI partition table, with "secure boot" turned on. Supposedly this is to ensure that the bootloader of your operating system has not been compromised. Its real purpose is to ensure Microsoft has an unbreakable hold on people's systems and their data, and lock-out competing operating systems and third-party self-booting rescue, repair and recovery programs.
First, this excludes older computers that use older BIOSes since manufacturers have only had it since 2009, and some people are using computers older than this. That's only a minor issue. A bigger issue in the mandate that secure boot be turned on, and TPM installed, to even use the system at all.
What is Secure Boot? Ostensibly, it allows you to know that your operating system was not "hacked," i.e. compromised. The bootloader, which is software on the disk that runs after the machine startup, to load the operating system, must be digitally signed with an electronic key, stored in the firmware of the computer. The firmware on every computer has only the key for Microsoft Windows, and no other operating system. They do not support any other system on PCs. Granted, for the vast majority of people who won't run anything else, that's not an issue. Right now, people who want to run Linux (or BSD, or any other operating system) can turn secure boot off. Now, it is possible you could boot Linux with secure boot off, then push the keys into the TPM. The reason it's possible is that Microsoft signed a secondary key for a Linux bootloader to use.
This means that users wanting to run Linux on the computer they own have to have Microsoft's permission. This also applies for anything else they might want to run. There are many diagnostic, repair, and recovery tools, that, by their nature, are booted instead of an operating system, and do not use Linux. Is Microsoft willing to sign the boot loader every time a toolmaker releases a new binary?
Small developers, open source, and free software developers should not have to get Microsoft to sign the software they create, for you to be able to run it on the computer you own. Now that's one thing. Another is the Trusted Platform Module. It's used to store security keys. Or security information. Windows 10 Credential Manager will store your credentials in the TPM if it's on the computer, instead of on disk.
But, here is the problem; with TPM turned on, and secure boot enabled, Windows will use the Bitlocker software - turned on by default - to encrypt the hard drive. This means the data is scrambled, making it impossible for Linux or third-party diagnostic tools to have access to your data. Where is the encryption key stored? In the TPM, of course. What happens if something goes wrong with the hardware? Right, your data is scrambled, and effectively lost, because it's encrypted, nothing else can access it. Now, it is possible to try to do BitLocker recovery, because they may have stored a backup copy of the password. But where? In the Microsoft account, you're forced to sign up for when you get a Windows PC that's connected to the Internet, whether or not you want one. You are forced to authenticate to Microsoft to be able to access your data on your computer. Another way Microsoft wants to have control over you.
Supposedly, the Trusted Platform Module is to allow the user to trust the software is authentic. But it's worse than that. It's so that Microsoft and other large software companies, and hardware manufacturers, to trust that your computer will do what they want, even if it is against your wishes, even though it is your computer that you own.
With secure boot and TPM enabled, you can no longer do what you want with your computer; Microsoft has total control over what is allowed.
There's much more, and I think it's worth watching.
https://youtu.be/LcafzHL8iBQ