The much maligned “Trusted Computing” idea requires that the party you are supposed to trust deserves to be trusted, and Google is DEFINITELY NOT worthy of being trusted, this is a naked power grab to destroy the open web for Google’s ad profits no matter the consequences, this would put heavy surveillance in Google’s hands, this would eliminate ad-blocking, this would break any and all accessibility features, this would obliterate any competing platform, this is very much opposed to what the web is.

  •  beefcat   ( @beefcat@beehaw.org ) 
    link
    fedilink
    English
    62
    edit-2
    1 year ago

    you need a Microsoft signed stub to boot anything other than Windows on a PC

    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.

    • 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.

      •  Hexorg   ( @Hexorg@beehaw.org ) 
        link
        fedilink
        English
        41 year ago

        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

      • 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.

    •  Gsus4   ( @Gsus4@lemmy.one ) 
      link
      fedilink
      English
      5
      edit-2
      1 year ago

      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.

          • 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

      •  beefcat   ( @beefcat@beehaw.org ) 
        link
        fedilink
        English
        2
        edit-2
        1 year ago

        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.

        •  Gsus4   ( @Gsus4@lemmy.one ) 
          link
          fedilink
          English
          2
          edit-2
          1 year ago

          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.

              •  wim   ( @wim@lemmy.sdf.org ) 
                link
                fedilink
                English
                81 year ago

                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.

              •  wim   ( @wim@lemmy.sdf.org ) 
                link
                fedilink
                English
                21 year ago

                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.

          • 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?