403WebShell

403Webshell

Server IP : 13.127.148.211 / Your IP : 216.73.216.113
Web Server : Apache/2.4.41 (Ubuntu)
System : Linux ip-172-31-43-195 5.15.0-1084-aws #91~20.04.1-Ubuntu SMP Fri May 2 06:59:36 UTC 2025 x86_64
User : www-data ( 33)
PHP Version : 7.4.3-4ubuntu2.29
Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON
Directory : /var/lib/dpkg/info/

Upload File :

[ Back ]

Current File : /var/lib/dpkg/info/shim-signed.templates

Template: shim/title/secureboot
Type: text
Description: Configuring Secure Boot

Template: shim/error/bad_secureboot_key
Type: error
Description: Invalid password
 The Secure Boot key you've entered is not valid. The password used must be
 between 8 and 16 characters.

Template: shim/enable_secureboot
Type: boolean
Default: false
Description: Enroll a new Machine-Owner Key?
 A new Machine-Owner key has been generated for this system to use when
 signing third-party drivers. This key now needs to be enrolled in your
 firmware, which will be done at the next reboot.
 .
 If Secure Boot validation was previously disabled on your system, validation
 will also be re-enabled as part of this key enrollment process.

Template: shim/secureboot_explanation
Type: note
Description: Your system has UEFI Secure Boot enabled.
 UEFI Secure Boot requires additional configuration to work with third-party
 drivers.
 .
 The system will assist you in configuring UEFI Secure Boot. To permit the
 use of third-party drivers, a new Machine-Owner Key (MOK) has been generated.
 This key now needs to be enrolled in your system's firmware.
 .
 To ensure that this change is being made by you as an authorized user, and
 not by an attacker, you must choose a password now and then confirm the
 change after reboot using the same password, in both the "Enroll MOK" and
 "Change Secure Boot state" menus that will be presented to you when this
 system reboots.
 .
 If you proceed but do not confirm the password upon reboot, Ubuntu
 will still be able to boot on your system but any hardware that requires
 third-party drivers to work correctly may not be usable.

Template: shim/secureboot_key
Type: string
Description: Enter a password for Secure Boot. It will be asked again after a reboot.

Template: shim/secureboot_key_again
Type: string
Description: Enter the same password again to verify you have typed it correctly.

Template: shim/error/secureboot_key_mismatch
Type: error
Description: Password input error
 The two passwords you entered were not the same. Please try again.

Youez - 2016 - github.com/yon3zu
LinuXploit