923
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Jul 2023
923 points (100.0% liked)
Technology
37708 readers
146 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
THIS IS NOT (just) ABOUT GOOGLE
Currently, attestation and "trusted computing" are already a thing, the main "sources of trust" are:
This is already going on, you need a Microsoft signed stub to boot anything other than Windows on a PC, you need Apple's blessing to boot anything on a Mac, your smartphone manufacturer decides whether you can unlock it and lose attestation, all of Microsoft, Apple and Google run app attestation through their app stores, several governments and companies run attestation software on their company hardware, and so on.
This is the next logical step, to add "web app" attestation, since the previous ones had barely any pushback, and even fanboys of walled gardens cheering them up.
PS: Somewhat ironically, Google's Play Store attestation is one of the weaker ones, just look at Apple's and the list of stuff they collect from the user's device to "attest" it for any app.
Not necessarily, most motherboards and laptops (at least every single one I've ever owned) allow users to enroll their own Secure Boot keys and maintain an entirely non-Microsoft chain of trust. You can also disable secure boot entirely.
Major distros like Ubuntu and Fedora started shipping with Microsoft-signed boot shims as a matter of convenience, not necessity.
Secure Boot itself is not some nefarious mechanism, it is a component of the open UEFI standard. Where Microsoft comes in to play is the fact that most PC vendors are going to pre-enroll Microsoft keys because they are all shipping computers with Windows, and Microsoft wants Secure Boot enabled by default on machines shipping with with their operating system.
For now. They're boiling the frog slow.
Microsoft doesn't control the standard, and the entire rest of the industry has no reason to ban non-Windows operating systems.
Widnows doesn't have the stranglehold over the market that it once did.
It's not just Microsoft, it's capitalists in general.
I hope you're right. Microsoft could try incentivising a shift.
The entire internet depends on machines running linux as servers. I highly doubt that any company has the power to change that
Yeah, it's not likely for server racks. Laptops, though, seem somewhat plausible. I'm actually pretty happy with the momentum on tech issues now, on the other hand. I hear stories about right to repair in normal media, my country is in a straight-up showdown with big tech, and GDPR is well established.
Windows 11 is saying you're required to have tpm 2.0 enabled in your bios in order to upgrade. Didn't know what it was on my self built computer until recently when windows said my system wasn't compatible to upgrade.
Tpm modules are pretty good. And you can buy them separately like another card. Motherboards usually have a slot for them. They are tiny like usb drives. They essentially are usb derives but for your passwords and keys. You can even configure Firefox to store your passwords in tpm
TPMs are a security threat. If malware manages to infiltrate it, then that malware is now impossible to remove and has unfettered access to the entire system. You have to junk the entire computer.
No they don’t. Worst case known attacks have resulted in insecure keys being generated. And even if malware could somehow be transferred out of it you wouldn’t have to trash your whole computer - just unplug the TPM
I'm afraid you are sorely mistaken. Here's an RCE vulnerability in the TPM 2.0 reference implementation.
Your own article says it’s VMs. The tpm itself can be bricked. Ok that sucks. Still not persistent like you describe.
The vulnerability is not specific to VMs. Malicious code running with privileges on the host operating system can also exploit it.
But yes, this can also be used to escape the VM sandbox, and since the TPM has full access to the entire system, exploit code can then gain full privileges on the host.
Can the TPM firmware not write to the flash where it's stored? If it can, then an RCE exploit can do so too, and thereby make itself persistent.
Basically, any successful RCE exploit in a TPM equals total and permanent compromise of the entire physical machine. That's why the TPM is a security threat rather than a security feature.
TPM and SecureBoot are separate UEFI features. Windows 11 requires TPM 2.0. If your system meets the CPU requirements, then it should support this without needing to install a hardware TPM dongle. However, until recently, many vendors turned had this feature turned off for some reason.
Where some confusion comes in is another Windows 11 requirement, that machines be SecureBoot capable. What this actually means in practice is that your system needs to be configured to boot in UEFI mode rather than CSM ("Legacy BIOS") mode.
You can't disable secure boot if you want to use your Nvidia GPU :( though. [edit2: turns out this is a linux mint thing, not the case in Debian or Fedora]
Edit: fine, there may be workarounds and for other distros everything is awesome, but in mint and possibly Ubuntu and Debian for a laptop 2022 RTX3060 you need to set up your MOK keys in secure mode to be able to install the Nvidia drivers, outside secure mode the GPU is simply locked. I wasn't even complaining, there is a way to get it working, so that's fine by me. No need to tell me that I was imagining things.
Hogwash. Running Fedora on closed source nvidia drivers with secure boot disabled.
"works for me"
What does that even mean?! Yes it works for me. That’s the whole bloody point of saying it. Someone was saying “it won’t work for anyone” and I was saying “well it works for me”.
“We can’t land at the moon!” “Eh, we already have” “‘Works for me’, so that’s not really valid”
Head_scratch.gif
My experience is that Nvidia plays nicer without secure boot. Getting Fedora up and running with the proprietary Nvidia drivers and fully working SecureBoot was quite a headache, whereas everything just worked out of the box when I disabled it.
But this is very much an Nvidia problem and not a SecureBoot problem. There is a reason basically no-one else provides their drivers as one-size-fits-all binary kernel modules.
Source?
Me installing Linux Mint on a 2022 laptop with a Nvidia GPU (had windows 11 preinstalled, this was an alongside install). I disabled secure boot at first, but still had to go all the way back and set up my MOK keys and turn on secure boot properly with another password to unlock the GPU.
Pro tip if you want to use Linux: don't rely on non-free drivers.
That's not a protip. A protip would be how you do that :D
Literally buy anything but Nvidia. Intel, AMD have upstream drivers that work regardless of secure boot. Various ARM platforms also have free drivers.
It used to be that there waa only bad choices, now there really is only one bad choice left.
Intel Arc still has some teething problems, particularly with power management on laptops, but AMD has been smooth sailing for almost a decade now.
Please help me understand why this is such a huge issue.
For many reasons. Nvidia requiring secure boot in this case, which is not available for all distros or kernels on all computers.
The other is requiring a workable kernel module and user space component from Nvidia, which means that as soon as Nvidia deprecates your hardware, you're stuck with legacy drivers, legacy kernels, or both.
Nvidia also has it's own separate userspace stack, meaning it doesn't integrate with the whole DRM & Mesa stack everyone else uses. For the longest time that meant no Wayland support, and it still means you're limited to Gnome only on wayland when using Nvidia AFAIK.
Another issue is switcheable graphics. Since systems with switchable graphics typically combine a Mesa based driver stack (aka everyone but Nvidia, but typically this would be AMD or Intel integrated graphics) with an Nvidia one, it involves swapping out the entire library chain (OpenGL or Vulkan or whatever libraries). This is typically done by using ugly hacks (wrapper scripts using LD_PRELOAD for example) and are prone to failure. Symptoms can be anything as mild as everything running on the integrated graphics, the discrete graphics never sleeping causing poor battery life or high power consumption, to booting to a black screen all or some of the time.
If these things don't bother you or you have no idea what these things mean, or you don't care about them or your hardware lasting more than 3-5y then it probably isn't a big deal to you. But none of the above exist when using Intel, AMD or a mix of those two.
In my experience the past twenty years, proprietary drivers are the root cause of I would say 90% of my issues using Linux.
When are people gonna learn to stop buying NVIDIA products?
Never heard of this before and couldn't find anything about secure boot being required to be enabled to use the Nvidia drivers with Linux.
But since you used dual boot you need to have secure boot enabled anyway, because win 11 would not work without it, would it?
https://forums.linuxmint.com/viewtopic.php?t=343833
You can search duckduckgo for Nvidia mok secure boot mint and you'll see what I'm talking about.
https://unix.stackexchange.com/questions/535434/what-exactly-is-mok-in-linux-for#535440
This is about signing the driver when secure boot is enabled. It doesn't say that Nvidia won't work with secure boot disabled.
I'm using Nvidia with debian and secure boot disabled btw. So the statement, "Nvidia won't work with secure boot disabled" is still wrong. Might be some Linux mint bug, but not a problem of Nvidia per se
fair enough, I had not tested any other distros, my bad.
I used fedora in 2022 with an Nvidia GPU and used the proprietary drivers just fine. Perhaps there was something different between your system and mine. Newer GPU perhaps? Mine was a 1080.
RTX3060, I suspect this is the case for newer laptops, yes.