Repository :
http://git.fedorahosted.org/git/?p=docs/uefi-secure-boot-guide.git
On branch : master
---------------------------------------------------------------
commit 178e52899a2b24b810f5d76185674470be11c4e2
Author: Eric Christensen <sparks(a)fedoraproject.org>
Date: Fri Feb 1 17:28:32 2013 -0500
Changed grub2 to GRUB
---------------------------------------------------------------
en-US/Implementation_of_Secure_Boot.xml | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/en-US/Implementation_of_Secure_Boot.xml
b/en-US/Implementation_of_Secure_Boot.xml
index 80c70ed..bceb9fe 100644
--- a/en-US/Implementation_of_Secure_Boot.xml
+++ b/en-US/Implementation_of_Secure_Boot.xml
@@ -27,8 +27,8 @@ to its complexity. Here is how the various components are signed.
control over this key. The shim contains the Fedora Boot CA public key.
</para>
<para>
- Grub2: This is signed by the "Fedora Boot Signer" key, which chains
-off the Fedora Boot CA key. Grub2 doesn't contain any keys, it calls into
+ GRUB: This is signed by the "Fedora Boot Signer" key, which chains
+off the Fedora Boot CA key. GRUB doesn't contain any keys, it calls into
shim for its verification.
</para>
<para>
@@ -42,7 +42,7 @@ build.
</para>
<para>
The Fedora Boot CA which is used to verify the
-integrity of grub2 and the kernel. This key can currently be found in the
+integrity of GRUB and the kernel. This key can currently be found in the
shim source package. The details of the key are:
<screen>
Certificate:
@@ -135,11 +135,11 @@ Microsoft has stated that the blacklist is to be used to prevent
binaries
being used for attacks from executing.
</para>
<para>
- In both boot methods, shim, grub2, and the kernel will detect that they
+ In both boot methods, shim, GRUB, and the kernel will detect that they
are started in what UEFI describes as "User mode" with Secure Boot enabled,
and upon detecting this they will validate the next stage with a
&PRODUCT;-specific cryptographic public key before starting it. The validation
-is done via shim for grub2, and grub2 calls back to shim to validate the
+is done via shim for GRUB, and GRUB calls back to shim to validate the
kernel as well. Once the kernel is booted, it will also detect that it is
in Secure Boot mode, which will cause several things to be true:
<simplelist>