Some options can be changed on active mappings using cryptsetup refresh. For plain dm-crypt devices the cipher, hash and size options are The supported options areĭescribed below. The fourth field, options, is an optional comma-separated list of options and/or flagsĭescribing the device type ( luks, tcrypt, bitlk, or plain which is also the default) andĬryptsetup options associated with the encryption process.
In this case, the options check, checkargs and tries may be useful. If the key file is the string none, a passphrase will be read interactively from theĬonsole. Persistent key and therefore does not support random data keys. dev/urandom), note however that LUKS requires a Passphrase the passphrase must not be followed by a newline character.
Note that the entire key file will be used as the Values with spaces and special characters need to be escaped using octal In case of a keyscript, the value of this field is given as argument to The third field, key file, describes the file to use as a key for decrypting the data of LABEL, PARTUUID and PARTLABEL) is supported as well, using “UUID=” (resp. Instead of giving the source device explicitly, the UUID The second field, source device, describes either the block special device or file thatĬontains the encrypted data. Source device will be created at /dev/mapper/target by cryptsetup. A mapped device which encrypts/decrypts data to/from the The first field, target, describes the mapped device name. Order of records in crypttab is important because the init scripts sequentially iterate Lines starting with “#” are comments, empty lines are ignored. Each filesystem is described on a separate line fields on each line are separatedīy tabs or spaces. Written it is the duty of the system administrator to properly create and maintain thisįile. cryptdisks_start and cryptdisks_stop), and not The file /etc/crypttab contains descriptive information about encrypted filesystems.Ĭrypttab is only read by programs (e.g. Provided by: cryptsetup_2.3.6-0ubuntu1_amd64Ĭrypttab - static information about encrypted filesystems
0 kommentar(er)
