Differences between revisions 24 and 25
Revision 24 as of 2019-01-15 15:45:09
Size: 5891
Comment:
Revision 25 as of 2019-01-15 15:57:37
Size: 7169
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Test procedure on an existing system = = Test procedure on an existing installation =
Line 79: Line 79:
= Tested hardware = == Tested hardware ==
Line 87: Line 87:
    * Dell XPS 13 2013 (L322X) '''failed at 5.'''     * Dell XPS 13 2013 (L322X) '''failed at 5.'''
Line 133: Line 133:

= Buster installer images =

Since '''14th Jan 2019''', our normal daily and weekly amd64 debian-installer images should boot and install correctly with Secure Boot enabled '''without''' needing any special steps.

See

 * https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/ (daily netinst build)
 * https://get.debian.org/images/weekly-builds/ (weekly full builds)

'''If you test with one of these, please note the exact version (date) that you used.'''

== Tested hardware ==

 1. Home-build PC using AsRock mainboard (H97 Pro4 P1.60) boots fine, installs fine using netinst and xfce CD images from 2019-01-14

= Buster live images =

Since '''15th Jan 2019''', our normal weekly amd64 live images should live-boot with Secure Boot enabled '''without''' needing any special steps.

There are still a couple of remaining niggles remaining to do a full working Secure Bootable installation from these live images yet...

See https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/

'''If you test with one of these, please note the exact version (date) that you used.'''

== Tested hardware ==

 1. Home-build PC using AsRock mainboard (H97 Pro4 P1.60) live-boots fine with gnome live image from 2019-01-15

Test procedure on an existing installation

For testing the secure boot feature on a real hardware, the steps below were followed:

1. First of all, a system running an up-to-date Debian unstable is needed

2. Install shim, grub and linux signed packages from unstable:

   1 $ apt install shim-signed grub-efi-amd64-signed linux-image-4.19.0-1-amd64

3. Download the test certificate:

   1 $ wget https://salsa.debian.org/kernel-team/linux/raw/debian/4.19.9-1/debian/certs/test-signing-certs.pem

4. Convert the cerficate to DER format:

   1 $ openssl x509 -outform der -in test-signing-certs.pem -out test-signing-certs.der

5. Import the test DER certificate as a MOK (Machine Owner Key). There are 2 steps to follow :

  • 1) Install mokutil and import the certificate using it:

   1 $ mokutil --import test-signing-certs.der
  • The last command requires to set an ephemeral password to confirm that the user at the console is indeed the person who requested the key import. This password only survives across a single run of mokmanager (mmx64.efi) and is cleared as soon as the process is completed or cancelled.
  • 2) Place the certificate in /boot/efi/EFI/debian and reboot. shim should now automatically launch the mokmanager tool.

    If it doesn't, you can manually launch it through an EFI shell. You can download an EFI shell from the Tianocore project. You may want to resort to a user-friendly boot manager like refind to get a menu at boot time. From the EFI shell you can launch mokmanager by running the following command:

Shell> fs0:\EFI\debian\mmx64.efi
  • Then, perfom the actions below:
    • Select the option Enroll key from disk.

    • Select the disk option that represents your EFI partition.
    • Go to EFI/debian directory.

    • Select test-signing-certs.der.

    • Select Continue and confirm the action (Yes). You'll be prompted for the password you typed in earlier when running mokutil.

  • Now, our test certificate is enrolled and you can select Continue boot. To exit from EFI shell run:

Shell> exit

6. Enable Secure boot

7. Reboot the machine and enjoy the Secure boot feature :)

Do not forget to check if grub is loading the signed linux image 4.19.0-1-amd64. You can also run the following command to check the Secure Boot status :

   1 $ mokutil --sb-state

Tested hardware

The steps above were performed in the following hardware until now:

  • ?ThinkPad X230

  • Minnowboard Turbot
  • HP 250 G4 (using method b)
  • ASUS ?ZenBook Pro 15 UX550GE

  • Dell XPS 13 2013 (L322X) failed at 5.

    • [2019-01-08] tested by coucouf
      • mokutil fails with message Failed to enroll new keys and return code 255 after giving a new password twice

      • no visible way to get to a UEFI shell on that machine for method b)
  • ?ThinkPad Yoga12

  • Home-build PC using ?AsRock mainboard (H97 Pro4 P1.60) (using method b)

  • ?ThinkPad T480

  • ?ThinkPad A285

    • [2019-01-09] tested by Haruki TSURUMOTO
      • mokutil was failed.

  • HP ?EliteBook 840 G3

    • 5a fails: mokutil fails with Failed to enroll new keys

    • 5b works. No EFI shell available by default, but it was possible to launch mmx64.efi via "Boot from file" in the boot menu.
  • Dell Inspiron 15 - 5547
    • 5a works
  • Schenker S403 (Clevo W840SN based)
    • Tested and works with cat /etc/issue : Debian GNU/Linux buster/sid

    • shim-signed had to be installed; grub-efi-amd64-signed linux-image-4.19.0-1-amd64 were already installed with default Debian Buster preview installer

    • 5b works, 5a possibly fails
    • 5a: mokutil fails with Failed to enroll new keys; moreover, trying mokutil --password fails with Failed to write MokPW

    • 5b:
      1. after copying the certificate test-signing-certs.der to /boot/efi/EFI/debian and rebooting the mokmanager tool launches and certificates waiting to be imported can be selected, i.e. it was not necessary to select a file

      2. However, i.a., it shows the following

        Issuer: CN=secure-boot-test-key-lfaraone
                Validity
                    Not Before: Apr  8 09:46:38 2018 GMT
                    Not After : May  8 09:46:38 2018 GMT
      3. Leaving the menus with escape key seemed to not stop the import
    • Anyway, after rebooting and enabling Secure Boot Custom, Grub boots Debian and mokutil --sb-state shows SecureBoot enabled

    • mokutil --list-enrolled lists two certificates:

      • the first one as above with [key 1]

      • the second one with [key 2] having, i.a.,

        Issuer: CN=Debian Secure Boot CA
                Validity
                    Not Before: Aug 16 18:09:18 2016 GMT
                    Not After : Aug  9 18:09:18 2046 GMT
    • Last, VirtualBox seems to be broken due to missing virtualbox-dkms

  • ASUS UX561UAR

Buster installer images

Since 14th Jan 2019, our normal daily and weekly amd64 debian-installer images should boot and install correctly with Secure Boot enabled without needing any special steps.

See

If you test with one of these, please note the exact version (date) that you used.

Tested hardware

  1. Home-build PC using ?AsRock mainboard (H97 Pro4 P1.60) boots fine, installs fine using netinst and xfce CD images from 2019-01-14

Buster live images

Since 15th Jan 2019, our normal weekly amd64 live images should live-boot with Secure Boot enabled without needing any special steps.

There are still a couple of remaining niggles remaining to do a full working Secure Bootable installation from these live images yet...

See https://get.debian.org/images/daily-builds/daily/current/amd64/iso-cd/

If you test with one of these, please note the exact version (date) that you used.

Tested hardware

  1. Home-build PC using ?AsRock mainboard (H97 Pro4 P1.60) live-boots fine with gnome live image from 2019-01-15