File: cryptroot-conf

package info (click to toggle)
cryptsetup 2%3A1.7.3-4
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 3,824 kB
  • sloc: ansic: 17,818; sh: 3,731; xml: 654; makefile: 517; python: 90; perl: 76
file content (34 lines) | stat: -rw-r--r-- 1,095 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
#
# 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=