From 4f813b4c1317ccf52cc41722211ce5e881393e14 Mon Sep 17 00:00:00 2001 From: JanKeller1 Date: Thu, 19 Jan 2017 15:07:40 -0800 Subject: [PATCH] Updated a mention of Windows 8 --- windows/keep-secure/bitlocker-countermeasures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/bitlocker-countermeasures.md b/windows/keep-secure/bitlocker-countermeasures.md index a928d5da12..89261d666c 100644 --- a/windows/keep-secure/bitlocker-countermeasures.md +++ b/windows/keep-secure/bitlocker-countermeasures.md @@ -53,7 +53,7 @@ Using the digital signature, UEFI verifies that the bootloader was signed using If the bootloader passes these two tests, UEFI knows that the bootloader isn’t a bootkit and starts it. At this point, Trusted Boot takes over, and the Windows bootloader, using the same cryptographic technologies that UEFI used to verify the bootloader, then verifies that the Windows system files haven’t been changed. -All Windows 8–certified devices must meet several requirements related to UEFI-based Secure Boot: +Starting with Windows 8, certified devices must meet several requirements related to UEFI-based Secure Boot: - They must have Secure Boot enabled by default. - They must trust Microsoft’s certificate (and thus any bootloader Microsoft has signed).