X-Git-Url: https://code.delx.au/refind/blobdiff_plain/1c723f224b1bc771a4192a2679831c7a6d21c264..bfe73b5fa6321273b7cf86b02a3c2d114a167bc9:/docs/refind/secureboot.html diff --git a/docs/refind/secureboot.html b/docs/refind/secureboot.html index fc3f321..09d382a 100644 --- a/docs/refind/secureboot.html +++ b/docs/refind/secureboot.html @@ -228,7 +228,7 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr

Installing Shim and rEFInd

-

Note: rEFInd's install.sh script attempts to identify whether your computer was booted with Secure Boot active and, if it was, to locate existing Shim binaries and make use of whatever it finds. Thus, you may not need to explicitly set up Shim after you install rEFInd, although you will probably have to enroll rEFInd's key in your MOK list, as described shortly.

+

Note: rEFInd's refind-install script attempts to identify whether your computer was booted with Secure Boot active and, if it was, to locate existing Shim binaries and make use of whatever it finds. Thus, you may not need to explicitly set up Shim after you install rEFInd, although you will probably have to enroll rEFInd's key in your MOK list, as described shortly.

A working Secure Boot installation of rEFInd involves at least three programs, and probably four or more, each of which must be installed in a specific way:

@@ -244,7 +244,7 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr -

If you've installed a distribution that provides Shim and can boot it with Secure Boot active, and if you then install rEFInd using the RPM file that I provide or by running install.sh, chances are you'll end up with a working rEFInd that will start up the first time, with one caveat: You'll have to use MokManager to add rEFInd's MOK to your MOK list, as described shortly. If you don't already have a working copy of Shim on your ESP, your task is more complex. Broadly speaking, the procedure should be something like this:

+

If you've installed a distribution that provides Shim and can boot it with Secure Boot active, and if you then install rEFInd using the RPM file that I provide or by running refind-install, chances are you'll end up with a working rEFInd that will start up the first time, with one caveat: You'll have to use MokManager to add rEFInd's MOK to your MOK list, as described shortly. If you don't already have a working copy of Shim on your ESP, your task is more complex. Broadly speaking, the procedure should be something like this:

    @@ -262,7 +262,7 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr version, though; as noted earlier, it's inadequate for use with rEFInd.) -

    Tip: If you're running Linux, you can save some effort by using the install.sh script with its --shim /path/to/shim.efi option rather than installing manually, as in steps 4–6 of this procedure. If you've installed openssl and sbsign, using --localkeys will generate local signing keys and re-sign the rEFInd binaries with your own key, too. You can then use sbsign and the keys in /etc/refind.d/keys to sign your kernels or boot loaders.

    +

    Tip: If you're running Linux, you can save some effort by using the refind-install script with its --shim /path/to/shim.efi option rather than installing manually, as in steps 4–6 of this procedure. If you've installed openssl and sbsign, using --localkeys will generate local signing keys and re-sign the rEFInd binaries with your own key, too. You can then use sbsign and the keys in /etc/refind.d/keys to sign your kernels or boot loaders.

  1. Copy the shim.efi and MokManager.efi binaries to the directory you intend to use for rEFInd—for instance, @@ -333,7 +333,7 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr

    Managing Your MOKs

    -

    The preceding instructions provided the basics of getting rEFInd up and running, including using MokManager to enroll a MOK on your computer. If you need to sign binaries, though, you'll have to use additional tools. The OpenSSL package provides the cryptographic tools necessary, but actually signing EFI binaries requires additional software. Two packages for this are available: sbsigntool and pesign. Both are available in binary form from this OpenSUSE Build Service (OBS) repository, and many distributions ship with at least one of them. The following procedure uses sbsigntool. To sign your own binaries, follow these steps (you can skip the first five steps if you've successfully used install.sh's --localkeys option):

    +

    The preceding instructions provided the basics of getting rEFInd up and running, including using MokManager to enroll a MOK on your computer. If you need to sign binaries, though, you'll have to use additional tools. The OpenSSL package provides the cryptographic tools necessary, but actually signing EFI binaries requires additional software. Two packages for this are available: sbsigntool and pesign. Both are available in binary form from this OpenSUSE Build Service (OBS) repository, and many distributions ship with at least one of them. The following procedure uses sbsigntool. To sign your own binaries, follow these steps (you can skip the first five steps if you've successfully used refind-install's --localkeys option):

      @@ -341,8 +341,8 @@ Windows 8, this isn't an option for it. Unfortunately, the Shim and PreLoader pr normally comes in a package called openssl.)
    1. If you did not re-sign your rEFInd binaries with - install.sh's --localkeys option, type the following - two commands to generate your public and private keys: + refind-install's --localkeys option, type the + following two commands to generate your public and private keys: 
       $ openssl req -new -x509 -newkey rsa:2048 -keyout refind_local.key \
@@ -362,7 +362,7 @@ $ openssl x509 -in refind_local.crt -out refind_local.cer
     are equivalent, but are used by different
     tools—sbsigntool uses refind_local.crt to sign
     binaries, but MokManager uses refind_local.cer to enroll the
-    key. If you used install.sh's --localkeys option,
+    key. If you used refind-install's --localkeys option,
     this step is unnecessary, since these keys have already been created
     and are stored in /etc/refind.d/keys/.