• brezel@piefed.social
        link
        fedilink
        English
        arrow-up
        115
        arrow-down
        8
        ·
        4 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.
        • muusemuuse@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          15
          arrow-down
          34
          ·
          4 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
            18
            ·
            3 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.

          • Truscape@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            26
            arrow-down
            2
            ·
            edit-2
            4 days ago

            (1) Yeah, well the secure boot keys needed for Linux distributions expire in September (https://www.tomshardware.com/tech-industry/cyber-security/microsoft-signing-key-required-for-secure-boot-uefi-bootloader-expires-in-september-which-could-be-problematic-for-linux-users), so that seems like a sustainable solution, sure buddy.

            (3) What’s your income? What region of the world do you live in and what hardware is available to you? I’m still using an am4 platform PC as my daily driver because I can’t burn money. One of my buddies has an AM3 PC. Many people use modified surplus office PCs (especially in developing nations like South America or SEA), which don’t have secure boot as an option. Check your privilege, and maybe donate some of your spare hardware to those who need it, if you want to make this “a non issue” for everyone.

            (4) Yeah. I own my hardware, I configure my software. I gut Windows like a fish and keep it on a leash for these games, and use Linux for my work and for the games that respect the ecosystem.

            • muusemuuse@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              9
              arrow-down
              27
              ·
              edit-2
              4 days ago
              1. New keys have already been released and you can always just create and enroll your own damn keys. This is sensationalist nonsense.
              2. “Check my privilege” over secure boot? Calm down, Karen.
              3. I think gaming on PC is going to get interesting in the coming decade as Microsoft kicks third parties out of the kernel (thanks crowdstrike!) and more and more people just stop putting up with windows. Enterprise in the US is hooked but everyone else? Na, they are gonna drop it.

              Edit: these are listed as 1,3,and 4 in my post in voyager but lemmy shows 123. Interesting.

              • Truscape@lemmy.blahaj.zone
                link
                fedilink
                English
                arrow-up
                14
                ·
                4 days ago

                On the list thing, it seems that adding numbers with periods in a list seems to auto configure it to ascending numbers. That’s why I used (1) (3) (4). Weird, but I guess that’s the work around.

                Enrolling your keys doesn’t work btw, because battlefield checks which keys you enroll, only accepting the default MS keys. Also on the hardware front, it is a big problem for gamers on a sub-300 USD budget these days - the best deals are on legacy hardware or surplus office equipment, mainly AM3-AM4 era.

                • filcuk@lemmy.zip
                  link
                  fedilink
                  English
                  arrow-up
                  3
                  arrow-down
                  1
                  ·
                  3 days ago

                  The number list is how markdown works. You can enter all 1’s and it will automatically create ordered list.
                  Handy when you may need to edit list items, as you dont need to renumber even in plain text.
                  Markdown spec should allow for explicit number by using a bracket ‘)’ instead of a dot, but it may not work everywhere.
                  Let’s give it a go

                  3) start from 3  
                  1. Then  
                  1. Continue  
                  
                  1. start from 3
                  1. Then
                  2. Continue
          • Kazumara@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            3 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.

        • 9tr6gyp3@lemmy.world
          link
          fedilink
          English
          arrow-up
          12
          arrow-down
          17
          ·
          4 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
            18
            arrow-down
            5
            ·
            4 days ago

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

            • Miaou@jlai.lu
              link
              fedilink
              English
              arrow-up
              9
              ·
              3 days ago

              Most people who work IT don’t even know what a kernel is, tbf

              • tpyo@lemmy.world
                link
                fedilink
                English
                arrow-up
                3
                ·
                edit-2
                3 days ago

                I recently had an rfid scanner immediately rma-d back that had just been returned to us. The new issue was caused by a setting and not by a defect. I asked our IT/help desk if it WAS a setting that could be changed

                “I don’t know. I get the thing, I check these settings, I check those settings, that’s all I know”

                😑😑😑

                So me and another person are out of our equipment for another couple weeks while the scanner is sent back for “repairs” and the repair people will go “😑 tap tap tap idiots”

                (Edit: I know it’s a setting because I talked with the other person who uses it and I explained the issue and he let me know it is something he changes)

            • 9tr6gyp3@lemmy.world
              link
              fedilink
              English
              arrow-up
              8
              arrow-down
              2
              ·
              3 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
                ·
                2 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
                  2
                  ·
                  2 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.

              • _cryptagion [he/him]@quokk.au
                link
                fedilink
                English
                arrow-up
                4
                arrow-down
                1
                ·
                3 days ago

                And Microsoft is shutting out most third parties in the near future because of Crowdstrike, so Linux likely won’t be supporting Secure Boot in the future, even if someone did want to enable it for some odd reason.

                • cole@lemdro.id
                  link
                  fedilink
                  English
                  arrow-up
                  6
                  ·
                  3 days ago

                  Microsoft can’t stop you from signing images with your own keys.

                  That’s what I do, and it’s almost entirely automated on Linux these days.

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

                  Microsoft’s kicking third parties out of the kernel because of crowdstrike. Secure boot is a completely different thing Microsoft can’t kick people out of.

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

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

      • Kyrgizion@lemmy.world
        link
        fedilink
        English
        arrow-up
        40
        arrow-down
        7
        ·
        4 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
          ·
          4 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
            17
            arrow-down
            8
            ·
            4 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
              8
              arrow-down
              3
              ·
              4 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
                  ·
                  4 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
                    ·
                    4 days ago

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

                • Miaou@jlai.lu
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  3 days ago

                  Can’t access the bios with secure boot on (at least I could not on an old laptop I was refurbishing, thank god the owner could login into windows)

                  • jjjalljs@ttrpg.network
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    3 days ago

                    That’s unusual, I think. Every computer I’ve had that had it on, I was able to turn it off when I went to install Linux.

              • atticus88th@lemmy.world
                link
                fedilink
                English
                arrow-up
                2
                ·
                4 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
            ·
            4 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
              ·
              3 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
                ·
                3 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
                  ·
                  3 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
          ·
          4 days ago

          If you have physical access you have full access anyway

          No, encrypt your drives.

      • SoupBrick@pawb.social
        link
        fedilink
        English
        arrow-up
        18
        arrow-down
        5
        ·
        4 days ago

        It fucks with Linux. I literally just disabled it to resolve a driver install issue before this announcement was made.

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

          Linux can run with secure boot just fine though. Use your distros documentation to set it up.

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

          Secureboot doesn’t “fuck with Linux”. It does protect you from malware trying to install unsigned kernel modules.

          Apparently that driver is unsigned, which is not the normal case nowadays.

          • SoupBrick@pawb.social
            link
            fedilink
            English
            arrow-up
            8
            ·
            edit-2
            4 days ago

            Good to know, thanks

            I was trying to install an Nvidia driver on Linux Mint, so I think I am safe.

              • Oisteink@feddit.nl
                link
                fedilink
                English
                arrow-up
                1
                ·
                4 days ago

                This happens to roughly 1/3rd of all pc’s. But if you put secureboot ON and the FBI cant touch your pc

            • frongt@lemmy.zip
              link
              fedilink
              English
              arrow-up
              1
              ·
              4 days ago

              This type of attack has been seen in the wild for quite some time. Ultimately it’s a security vs convenience decision.