OXIESEC PANEL
- Current Dir:
/
/
etc
/
cryptsetup-initramfs
Server IP: 10.0.0.4
Upload:
Name
Size
Modified
Perms
Actions
📁
..
-
01/22/2024 08:17:32 AM
rwxr-xr-x
📄
conf-hook
1.07 KB
08/23/2018 02:36:42 PM
rw-r--r--
Delete
Editing: conf-hook
Close
# # Configuration file for the cryptroot initramfs hook. # # # CRYPTSETUP: [ y | n ] # # Add cryptsetup modules to the initramfs image, regardless of _this_ # machine configuration. By default, cryptsetup modules are only added # when there is a device that needs to be unlocked at initramfs stage # (such as root or resume devices). # #CRYPTSETUP= # # 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.) # # Setting KEYFILE_PATTERN to a non-empty value implies "CRYPTSETUP=y". # # 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=