REDROOM
PHP 8.5.2
Path:
Logout
Edit File
Size: 995 B
Close
//usr/share/doc/secureboot-db/README.Debian
Text
Base64
secureboot-db for Ubuntu ------------------------ When Secure Boot is enabled, the bootloader must be signed by an entry in the Secure Boot DB. If the signature verifies and the entry does not appear in the DBX blacklist, the boot process is allowed to continue. Each stage of the boot process may also be verified against DB and DBX. DB and DBX will need to be updated for certificate updates and additions to the blacklist, and this package provides the mechanism do so. It works by adding signed updates to /usr/share/secureboot/updates and then runs sbkeysync on them. Eg: $ sudo sbkeysync --no-default-keystores \ --keystore /usr/share/secureboot/updates Note that this package tries to add all keys from the keystore that are not found in the key databases in firmware. When secure boot is enabled, updates to DB and DBX can only be performed if they are signed by an entry in the KEK database. -- Jamie Strandboge <jamie@ubuntu.com> Tue, 04 Dec 2012 13:22:03 -0600
Save
Close
Exit & Reset
Text mode: syntax highlighting auto-detects file type.
Directory Contents
Dirs: 0 × Files: 3
Delete Selected
Select All
Select None
Sort:
Name
Size
Modified
Enable drag-to-move
Name
Size
Perms
Modified
Actions
changelog.gz
835 B
lrw-r--r--
2024-04-08 16:19:02
Edit
Download
Rename
Chmod
Change Date
Delete
OK
Cancel
recursive
OK
Cancel
recursive
OK
Cancel
copyright
1.01 KB
lrw-r--r--
2023-11-09 10:02:47
Edit
Download
Rename
Chmod
Change Date
Delete
OK
Cancel
recursive
OK
Cancel
recursive
OK
Cancel
README.Debian
995 B
lrw-r--r--
2023-11-09 10:02:47
Edit
Download
Rename
Chmod
Change Date
Delete
OK
Cancel
recursive
OK
Cancel
recursive
OK
Cancel
Zip Selected
If ZipArchive is unavailable, a
.tar
will be created (no compression).