Linux localhost 5.4.0-198-generic #218-Ubuntu SMP Fri Sep 27 20:18:53 UTC 2024 x86_64
Apache/2.4.41 (Ubuntu)
: 23.92.16.63 | : 172.70.114.232
Cant Read [ /etc/named.conf ]
8.1.5
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
README
+ Create Folder
+ Create File
/
etc /
cryptsetup-initramfs /
[ HOME SHELL ]
Name
Size
Permission
Action
conf-hook
1
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : conf-hook
# # Configuration file for the cryptroot initramfs hook. # # # KEYFILE_PATTERN: ... # # The value of this variable is interpreted as a shell pattern. # Matching key files from the crypttab(5) are included in the initramfs # image. The associated devices can then be unlocked without manual # intervention. (For instance if /etc/crypttab lists two key files # /etc/keys/{root,swap}.key, you can set KEYFILE_PATTERN="/etc/keys/*.key" # to add them to the initrd.) # # If KEYFILE_PATTERN if null or unset (default) then no key file is # copied to the initramfs image. # # Note that the glob(7) is not expanded for crypttab(5) entries with a # 'keyscript=' option. In that case, the field is not treated as a file # name but given as argument to the keyscript. # # WARNING: If the initramfs image is to include private key material, # you'll want to create it with a restrictive umask in order to keep # non-privileged users at bay. For instance, set UMASK=0077 in # /etc/initramfs-tools/initramfs.conf # #KEYFILE_PATTERN=
Close