4 ms·
> Microsoft act as a Certification Authority (CA) for SB, and they will sign programs on behalf of other trusted organisations so that their programs will also
by hulitu 5y ago
> Microsoft act as a Certification Authority (CA) for SB, and they will sign programs on behalf of other trusted organisations so that their programs will also run.
This means: 1. You trust Microsoft (you delegate the trust of your data to Microsoft).
2. You trust that Microsoft certificate will not be revoked.
Sorry, for me, secure boot is when i have the keys. When someone else has them they also have my data.
- willis936 5y agoMicrosoft doesn't have access to your hardware. How would they exfiltrate your data without also having your TPM? If a key is revoked then you... disable secure boot.
- nix23 5y agoWhy do you trust a closed down chip like TPM, why do you trust secure-boot when the only time it's verifying the kernel is at boot time? Why trust something like IntelME? Why trust something like a proprietary UEFI?
- Koshkin 5y ago> Why do you trust Because most of the industry does, and companies have little choice in the matter. That's the power (and the convenience) of a monopoly. For your small-scale setup at home you are free to do as you wish (you can even use a RaspberryPi or whatever, although in such cases you are dealing with at least partially closed-source hardware anyway).
- nix23 5y ago>Because most of the industry does That's a pretty bad comparison in a time when every day 100's of "industry's" get ransomware'd. >That's the power (and the convenience) of a monopoly. No that's the week point and inconvenience of every brand monopoly.
- willis936 5y agoI don't trust anyone, especially boot drives that have been exposed to the internet. That's why I would like a system of trust between my hardware components until the OS takes over. Why do you trust your boot drive?
- nix23 5y ago>Why do you trust your boot drive? Because HIDS with my own signed hash database and hids-exec. But i cannot scan/proof what the UEFI TPM IntelME makes.
- voakbasda 5y agoYou do not understand how secure boot works. As a developer, I pick my own keys to use for signing on my devices. I do not trust Microsoft, but that’s moot: they have nothing to do with my use of secure boot. Source: I an a senior embedded engineer that has implemented secure boot for paying customers, across multiple devices and processor architectures. That said, I despise vendors that lock down their devices using secure boot. This is unquestionably hostile behavior toward consumers, as the protection from malware usually also prevents user modification. I wish there was a way to force disclosure of this anti-feature, as I actively avoid buying products that do not allow me to load my own keys and images.
- smoldesu 5y agoI think it's a lot more practical for most people to just set a BIOS password.
- temptemptemp111 5y agoDoes the Pixel (using GrapheneOS) prevent use of custom keys?