Remove out-of-date verified_boot.md

Verified boot has been documented here:

https://designs.apertis.org/latest/system-updates-and-rollback.html#verified-boot



Remove this page and link to the above information instead.

Signed-off-by: Martyn Welch <martyn.welch@collabora.com>

content/conditional_access/implementation.md

@@ -464,7 +464,8 @@ developer mode; it could merely make the device key inaccessible until
 the OS is replaced by a trusted one. However, it would still be
 necessary to delete app-bundles during the switch to developer mode.
 
-This is somewhat linked to [Verified boot]( {{< ref "/verified_boot.md" >}} )
+This is somewhat linked to
+[Verified boot](https://designs.apertis.org/latest/system-updates-and-rollback.html#verified-boot)
 ("secure boot"), which can verify whether the operating system being
 booted is a trusted one or not.
 
@@ -489,4 +490,4 @@ The same list of recently-used themes could be used when a current theme
 is uninstalled, if desired.
 
 The configuration application should not allow empty/deleted themes to
-be selected.
+be selected.
\ No newline at end of file

content/verified_boot.md

-+++
-date = "2015-12-02"
-weight = 100
-
-title = "Verified boot"
-
-aliases = [
-    "/old-wiki/Verified_boot"
-]
-+++
-
-[Verified
-boot](https://en.wikipedia.org/wiki/Hardware_restriction#Verified.2Ftrusted.2Fsecure_boot),
-also known as *trusted boot* or *secure boot*, uses cryptographic
-signatures to ensure that only approved software can run on particular
-hardware.
-
-A [concept design]( {{< ref "/conceptdesigns.md" >}} ) for verified boot on
-Apertis is not currently available, although the Security [concept
-design]( {{< ref "/conceptdesigns.md" >}} ) touches on this topic.
\ No newline at end of file