Announcement

Collapse
No announcement yet.

It's Looking Like UEFI SecureBoot Will Be Ready In Time For Debian 10.0 Buster

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • It's Looking Like UEFI SecureBoot Will Be Ready In Time For Debian 10.0 Buster

    Phoronix: It's Looking Like UEFI SecureBoot Will Be Ready In Time For Debian 10.0 Buster

    It looks like that by the time Debian 10.0 "Buster" rolls about in roughly one year, the UEFI SecureBoot support should be in good shape...

    http://www.phoronix.com/scan.php?pag...EFI-SecureBoot

  • #2
    Did they name Debian this time after a porn star ? I mean... Buster... Dolly Buster ?

    Comment


    • #3
      Originally posted by Candy View Post
      Did they name Debian this time after a porn star ? I mean... Buster... Dolly Buster ?
      As always, Debian codenames are based on the names of characters from the Toy Story film.
      Buster is Andy's dog: picture.

      Comment


      • #4
        I have once tried secure boot with custom keys on one machine and it turned out it could be easily disabled with a CMOS reset...

        Comment


        • #5
          Originally posted by Candy View Post
          Did they name Debian this time after a porn star ? I mean... Buster... Dolly Buster ?
          Or Buster from Mythbusters? But no, in this case it's Buster from Toy Story. Come on, dude...

          Comment


          • #6
            I wonder what happens when they run out of Toy story characters. Oh, wait, I almost forgot, Debian releases are like centuries apart.

            Comment


            • #7
              Originally posted by Xorg View Post
              Buster is Andy's dog: picture.
              At least the dog gets enough saussages from the Toy Story gang

              Comment


              • #8
                Originally posted by mb_q View Post
                I have once tried secure boot with custom keys on one machine and it turned out it could be easily disabled with a CMOS reset...
                Physical access = game over anyway. Secure Boot is supposed to protect against software attacks, for example substituting your bootloader/kernel/kernel modules.

                Comment


                • #9
                  Originally posted by Candy View Post
                  At least the dog gets enough saussages from the Toy Story gang
                  Go back to Rule34

                  Comment


                  • #10
                    Originally posted by numacross View Post
                    Physical access = game over anyway. Secure Boot is supposed to protect against software attacks, for example substituting your bootloader/kernel/kernel modules.
                    It's supposed to protect at least partially against "Evil Maid" type of physical attacks too.

                    Comment

                    Working...
                    X