3 ms·
What attestation the website accepts entirely depends on the configuration. There's nothing in the spec that will prevent attestations for Linux computers. Linu
by jeroenhd 3y ago
What attestation the website accepts entirely depends on the configuration. There's nothing in the spec that will prevent attestations for Linux computers. Linux already works perfectly fine with secure boot and such, I don't see why a signed bootloader starting a signed attestation engine wouldn't be trusted by third party websites.
It'll kill open platforms like the rare open source RISC-V implementations, but for almost any platform in use today this can be implemented.
The real question is "but will it", and in practice websites will probably only whitelist Chrome, Edge, and (reluctantly) Safari.
- codedokode 3y ago> I don't see why a signed bootloader starting a signed attestation engine wouldn't be trusted by third party websites. Do you mean a kind of Linux where root cannot do anything he wants? Like Android?
- jeroenhd 3y agoYes, a kind of Linux like Ubuntu or Fedora that already boots with secure boot enabled with full support of TPMs and similar technologies. The kind of Linux 99% of Linux users are running today. More secure variants like Android, leveraging SELinux and such, help with sandboxing but I don't think that SELinux is a struct requirement.
- raxxorraxor 3y agoThey are not more secure at all.
- codedokode 3y agoI mean if root can do anything then such system is not "trusted" from corporations point of view. Therefore, it won't be able to pass the attestation or play DRM content.
- hollerith 3y agoHuh? Fedora defaults to secure boot's being off and it is complicated to get it turned on. Even after you manage to turn it on, it only verifies the kernel and cannot do anything about malware hiding in /usr. There is no Linux distro AFIAK that has verification of the entire system like ChromeOS, MacOS, iOS, Android and Windows have.
- jeroenhd 3y agoFedora's own website [1] states: > Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can be installed and run on systems where UEFI Secure Boot is enabled. On UEFI-based systems with the Secure Boot technology enabled, all drivers that are loaded must be signed with a valid certificate, otherwise the system will not accept them. All drivers provided by Red Hat are signed by the UEFI CA certificate. Running your own secure boot CA is not enabled out of the box (for obvious reasons), but that does not pose a problem on most systems. Secure boot only needs special care if you need to load unsigned kernel modules (DKMS, Nvidia) or if you run on a super duper special Microsoft device that doesn't have the third party CA certificate by default. [1]: https://docs.fedoraproject.org/en-US/fedora/latest/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/#sec-UEFI_Secure_Boot https://docs.fedoraproject.org/en-US/fedora/latest/system-ad...
- hollerith 3y agoNothing you wrote contradicts anything I wrote. Specifically, although Fedora support secure boot, if you follow the standard install process, you will get a system with secure boot turned off. I know because I've installed Fedora on a system capable of secure boot. And, again, it is complicated to get it turned on. How complicated? Take a look: https://nwildner.com/posts/2021-04-10-secureboot-fedora/ https://nwildner.com/posts/2021-04-10-secureboot-fedora/ >The kind of Linux 99% of Linux users are running today. I severely doubt that even 5% of Linux installs have secure boot turned on because of how complicated it is to get it working. Specifically I imagine that the complicated instructions on the page I just linked will need to be modified depending on the specific secure-boot firmware.
- jasonjayr 3y agoLinux computers with an approved boot chain and software environment. Gentoo users are out, as is anyone making a custom kernel.
- macNchz 3y agoI imagine also anyone who, despite being on an approved distro, has had to enroll their own key to build and sign drivers as well.
- jeroenhd 3y agoGentoo users and people running Nvidia drivers and the like will be out, that's true. That's very different from "only certain architectures allowed", though. Even still, there are ways to implement this using an open source, signed, reproducibly built daemon that gets loaded early in the boot process. Altering the daemon would've out of the question but it would solve the more immediate problem of "Netflix doesn't work" that most people would actually care about.
- raxxorraxor 3y agoNetflix can only discriminate because we have attestation in the first place. This is not a security mechanism anymore.
- raxxorraxor 3y agoThis is exactly why people criticized secure boot. To not allow such system to establish themselves is the best defense. True for secure boot as well. Security is not the argument anymore, it is market domination.