• brezel@piefed.social
      link
      fedilink
      English
      arrow-up
      98
      arrow-down
      8
      ·
      15 days ago
      • some people run more than 1 OS
      • some people actually program and need to load unsigned shit all the time
      • some people have legacy hardware that doesn’t run with secureboot
      • it is my decision and my decision alone how i boot my operating systems. not EA’s.
      • 9tr6gyp3@lemmy.world
        link
        fedilink
        English
        arrow-up
        12
        arrow-down
        15
        ·
        15 days ago

        Im fairly certain any legacy hardware that doesn’t have secure boot as an option is going to struggle loading BF6 regardless.

        The first two points are not related to secure boot at all.

        • brezel@piefed.social
          link
          fedilink
          English
          arrow-up
          16
          arrow-down
          5
          ·
          15 days ago

          you think loading my own kernel modules is not related to secure boot? i guess you don’t work in IT then.

          • 9tr6gyp3@lemmy.world
            link
            fedilink
            English
            arrow-up
            8
            arrow-down
            2
            ·
            15 days ago

            It doesn’t matter which kernel modules are used, as long as you have signed those changes before rebooting.

            • Resonosity@lemmy.dbzer0.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              14 days ago

              Do you have any advice for someone that dual boots SteamOS and Windows 10 on a Steam Deck?

              I’ve heard online that since SteamOS manually signs keys or something, that if any changes happen to the kernel that later need to be updated by SteamOS, I’d need to re-sign the keys or whatever. Idk I’m not well versed in any of this

              I’ve heard it’s as easy as downloading the M$ keys to enable Secure Boot, but I also don’t want to brick my Deck.

              • muusemuuse@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                1
                ·
                14 days ago

                Windows 10 support is ending soon so there’s no reason to have it on your steam deck. Steam will stop supporting it sooner after Microsoft does, just like steam does with Apples operating system.

                  • muusemuuse@sh.itjust.works
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    13 days ago

                    No, they are killing it unless you pay and extra $30 a month and use a Microsoft account and kill local accounts.

          • troed@fedia.io
            link
            fedilink
            arrow-up
            6
            arrow-down
            1
            ·
            15 days ago

            Really? Which would those be? So far I haven’t come upon one.

      • muusemuuse@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        11
        arrow-down
        31
        ·
        15 days ago
        1. You can run more than one OS with secure boot enabled. It’s just a pain in the ass.
        2. you can run unsigned code on a secure boot enabled system.
        3. its 2025, what the fuck do you have that can’t secure boot by now?
        4. THIS is your winning argument.
        • Alaik@lemmy.zip
          link
          fedilink
          English
          arrow-up
          15
          ·
          15 days ago

          I don’t think he needs a winning argument. I think EA needs to justify this kernel level AC, not the other way around.

        • Kazumara@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          15 days ago

          You can run more than one OS with secure boot enabled. It’s just a pain in the ass.

          Weird, for me it was just flicking the switch in UEFI and now Grub and through it Windows 10 and Fedora 43 boot in Secure Boot.

    • Kyrgizion@lemmy.world
      link
      fedilink
      English
      arrow-up
      33
      arrow-down
      6
      ·
      15 days ago

      Needlessly intrusive. Can obviously be circumvented by cheaters anyway, so quite possibly superfluous. Apart from that it protects against the kinds of attacks that typically require physical access to the computer. If you have physical access you have full access anyway. Etc.

      • 9tr6gyp3@lemmy.world
        link
        fedilink
        English
        arrow-up
        22
        arrow-down
        3
        ·
        15 days ago

        If you have physical access you have full access anyway. Etc.

        You know secure boot was specifically made to protect users for this exact use case. Any tampering of the system will prevent the system from booting.

        • Eggymatrix@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          15
          arrow-down
          8
          ·
          15 days ago

          I get your pc, “tamper” it, then i install a fake bios that tells you all is well and that your tpm and secureboot and whatever else bullcrap they invent is still happy.

          See the problem?

          • Corngood@lemmy.ml
            link
            fedilink
            English
            arrow-up
            7
            arrow-down
            3
            ·
            15 days ago

            It won’t boot though, because the keys to decrypt the system are stored in the TPM.

            Sure you could replace the whole OS, but that’s going to be very obvious and won’t allow you access to the data.

              • PHLAK@lemmy.world
                link
                fedilink
                English
                arrow-up
                7
                arrow-down
                2
                ·
                15 days ago

                If you enable Secure Boot you should also set a BIOS password for this very reason.

                • Saleh@feddit.org
                  link
                  fedilink
                  English
                  arrow-up
                  12
                  arrow-down
                  1
                  ·
                  15 days ago

                  So, if you set a bios password either way, which benefit does secureboot give?

                  • AlphaOmega@lemmy.world
                    link
                    fedilink
                    English
                    arrow-up
                    4
                    ·
                    15 days ago

                    Not sure if this works these days, but on older systems there was a reset bios config jumper and pulling the cmos battery.

            • atticus88th@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              15 days ago

              Isnt it possible to have a recovery key? Isnt that technically a backdoor? Maybe the terms are not correct but there is a way in physically.

        • Limonene@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          1
          ·
          15 days ago

          A person with physical access can tamper with the OS, then tamper with the signing keys. Most secure boot systems allow you to install keys.

          Secure boot can’t detect a USB keylogger. Nothing can.

          • 9tr6gyp3@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            15 days ago

            The signature checks will immediately fail if ANY tampering has occurred.

            Adding a USB keylogger that has not been signed will cause a signature verification failure during boot.

            • Limonene@lemmy.world
              link
              fedilink
              English
              arrow-up
              2
              ·
              15 days ago

              A USB keylogger is not detectable by the computer, not in firmware nor operating system. It passively sniffs the traffic between the USB keyboard and the computer, to be dumped out later.

              • 9tr6gyp3@lemmy.world
                link
                fedilink
                English
                arrow-up
                1
                ·
                14 days ago

                If your keys are stored in the TPM for use during the secure boot phase, there will be nothing for it to log.

      • Tanoh@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        15 days ago

        If you have physical access you have full access anyway

        No, encrypt your drives.