Loading Documentation/device-mapper/dm-crypt.txt +2 −2 Original line number Diff line number Diff line Loading @@ -5,7 +5,7 @@ Device-Mapper's "crypt" target provides transparent encryption of block devices using the kernel crypto API. For a more detailed description of supported parameters see: http://code.google.com/p/cryptsetup/wiki/DMCrypt https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt Parameters: <cipher> <key> <iv_offset> <device path> \ <offset> [<#opt_params> <opt_params>] Loading Loading @@ -80,7 +80,7 @@ Example scripts =============== LUKS (Linux Unified Key Setup) is now the preferred way to set up disk encryption with dm-crypt using the 'cryptsetup' utility, see http://code.google.com/p/cryptsetup/ https://gitlab.com/cryptsetup/cryptsetup [[ #!/bin/sh Loading Documentation/device-mapper/verity.txt +2 −2 Original line number Diff line number Diff line Loading @@ -142,7 +142,7 @@ block boundary) are the hash blocks which are stored a depth at a time The full specification of kernel parameters and on-disk metadata format is available at the cryptsetup project's wiki page http://code.google.com/p/cryptsetup/wiki/DMVerity https://gitlab.com/cryptsetup/cryptsetup/wikis/DMVerity Status ====== Loading @@ -159,7 +159,7 @@ Set up a device: A command line tool veritysetup is available to compute or verify the hash tree or activate the kernel device. This is available from the cryptsetup upstream repository http://code.google.com/p/cryptsetup/ the cryptsetup upstream repository https://gitlab.com/cryptsetup/cryptsetup/ (as a libcryptsetup extension). Create hash on the device: Loading drivers/md/dm-crypt.c +1 −1 Original line number Diff line number Diff line Loading @@ -228,7 +228,7 @@ static struct crypto_ablkcipher *any_tfm(struct crypt_config *cc) * * tcw: Compatible implementation of the block chaining mode used * by the TrueCrypt device encryption system (prior to version 4.1). * For more info see: http://www.truecrypt.org * For more info see: https://gitlab.com/cryptsetup/cryptsetup/wikis/TrueCryptOnDiskFormat * It operates on full 512 byte sectors and uses CBC * with an IV derived from initial key and the sector number. * In addition, whitening value is applied on every sector, whitening Loading Loading
Documentation/device-mapper/dm-crypt.txt +2 −2 Original line number Diff line number Diff line Loading @@ -5,7 +5,7 @@ Device-Mapper's "crypt" target provides transparent encryption of block devices using the kernel crypto API. For a more detailed description of supported parameters see: http://code.google.com/p/cryptsetup/wiki/DMCrypt https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt Parameters: <cipher> <key> <iv_offset> <device path> \ <offset> [<#opt_params> <opt_params>] Loading Loading @@ -80,7 +80,7 @@ Example scripts =============== LUKS (Linux Unified Key Setup) is now the preferred way to set up disk encryption with dm-crypt using the 'cryptsetup' utility, see http://code.google.com/p/cryptsetup/ https://gitlab.com/cryptsetup/cryptsetup [[ #!/bin/sh Loading
Documentation/device-mapper/verity.txt +2 −2 Original line number Diff line number Diff line Loading @@ -142,7 +142,7 @@ block boundary) are the hash blocks which are stored a depth at a time The full specification of kernel parameters and on-disk metadata format is available at the cryptsetup project's wiki page http://code.google.com/p/cryptsetup/wiki/DMVerity https://gitlab.com/cryptsetup/cryptsetup/wikis/DMVerity Status ====== Loading @@ -159,7 +159,7 @@ Set up a device: A command line tool veritysetup is available to compute or verify the hash tree or activate the kernel device. This is available from the cryptsetup upstream repository http://code.google.com/p/cryptsetup/ the cryptsetup upstream repository https://gitlab.com/cryptsetup/cryptsetup/ (as a libcryptsetup extension). Create hash on the device: Loading
drivers/md/dm-crypt.c +1 −1 Original line number Diff line number Diff line Loading @@ -228,7 +228,7 @@ static struct crypto_ablkcipher *any_tfm(struct crypt_config *cc) * * tcw: Compatible implementation of the block chaining mode used * by the TrueCrypt device encryption system (prior to version 4.1). * For more info see: http://www.truecrypt.org * For more info see: https://gitlab.com/cryptsetup/cryptsetup/wikis/TrueCryptOnDiskFormat * It operates on full 512 byte sectors and uses CBC * with an IV derived from initial key and the sector number. * In addition, whitening value is applied on every sector, whitening Loading