We work with UEFI Secure Boot, let's say so. Closes: #919233

1 files changed, 3 insertions, 10 deletions

diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml
index 262e19f6c..6a3157f06 100644
--- a/en/preparing/pre-install-bios-setup.xml
+++ b/en/preparing/pre-install-bios-setup.xml
@@ -86,16 +86,9 @@ hardware; it is most critically invoked during the bootstrap process
       (potentially malicious) boot code that is unsigned or signed with
       unknown keys.  In practice the only key accepted by default on most
       UEFI systems with secure boot is a key from Microsoft used for signing
-      the Windows bootloader.  As the boot code used by &d-i; is not signed
-      by Microsoft, booting the installer requires prior deactivation of
-      secure boot in case it is enabled.  Secure boot is often enabled by
-      default on systems that come preinstalled with a 64-bit version of
-      Windows 8 and there is unfortunately no standard way to disable it
-      in the UEFI setup.  On some systems, the option to disable
-      secure boot is only made visible when a BIOS password has been set by
-      the user, so if you have a system with secure boot enabled, but cannot
-      find an option to disable it, try setting a BIOS password, powercycle
-      the machine and look again for an appropriate option.
+      the Windows bootloader.  Debian includes a <quote>shim</quote>
+      signed by Microsoft, so should work correctly on systems with
+      secure boot enabled.
     </para>
   </sect2>