Revert "Update README.md with answers to additional boothole questions"

This reverts commit 35699911a28c493a60857773ff0e8672903d04e3.
diff --git a/README.md b/README.md
index 3895539..7e0ae03 100644
--- a/README.md
+++ b/README.md
@@ -78,37 +78,3 @@
 -------------------------------------------------------------------------------
 Our shim-15.1 build is largely upstream's 15.1 with our new public certificate embedded.  This build has been tested with our new grub, which is now up-to-date with fedora-33.
 
--------------------------------------------------------------------------------
-If bootloader, shim loading is, grub2: is CVE-2020-10713 fixed ?
--------------------------------------------------------------------------------
-Yes.
-
--------------------------------------------------------------------------------
-If bootloader, shim loading is, grub2, and previous shims were trusting affected
-by CVE-2020-10713 grub2:
-* were old shims hashes provided to Microsoft for verification
-  and to be added to future DBX update ?
-* Does your new chain of trust disallow booting old, affected by CVE-2020-10713,
-  grub2 builds ?
--------------------------------------------------------------------------------
-1) Yes, our old hashes have been sent to Microsoft for verification via email to ueficamanualreview@microsoft.com.
-2) Our new chain of trust will utilize our new EV Code Signing certificate for the first time, which expires in 2022.  All vulnerable versions of grub that we have released to date have been signed with our old now-expired certificate (exp. 09/02/2020), so they will not be allowed to boot in our new chain of trust.
-
--------------------------------------------------------------------------------
-If your boot chain of trust includes linux kernel, is
-"efi: Restrict efivar_ssdt_load when the kernel is locked down"
-upstream commit 1957a85b0032a81e6482ca4aab883643b8dae06e applied ?
-Is "ACPI: configfs: Disallow loading ACPI tables when locked down"
-upstream commit 75b0cea7bf307f362057cc778efe89af4c615354 applied ?
--------------------------------------------------------------------------------
-1) Yes, 1957a85b0032a81e6482ca4aab883643b8dae06e is applied in our kernel (https://github.com/neverware/kernel/commit/1957a85b0032a81e6482ca4aab883643b8dae06e)
-2) Yes, this commit is applied in our kernel but appears as 824d0b6225f3fa2992704478a8df520537cfcb56 (https://github.com/neverware/kernel/commit/824d0b6225f3fa2992704478a8df520537cfcb56)
-
--------------------------------------------------------------------------------
-If you use vendor_db functionality of providing multiple certificates and/or
-hashes please briefly describe your certificate setup. If there are whitelisted hashes
-please provide exact binaries for which hashes are created via file sharing service,
-available in public with anonymous access for verification
--------------------------------------------------------------------------------
-We do not use this functionality.
-