diff options
| author | Andrii Pravorskyi <1227399-pravorskyi@users.noreply.gitlab.com> | 2021-05-11 00:07:36 +0300 |
|---|---|---|
| committer | Milan Broz <gmazyland@gmail.com> | 2021-05-17 17:54:47 +0200 |
| commit | a3f919bd25c823e6ae643000b9f7134dbd945840 (patch) | |
| tree | 8005dfe4c3d3c05d78b101c37c6587beb014c35e /man | |
| parent | 4f6f7404df87660493eaec0b60db466ad320b5af (diff) | |
| download | cryptsetup-a3f919bd25c823e6ae643000b9f7134dbd945840.tar.gz | |
Add a note about CRC32 and other non-cryptographic checksums
Diffstat (limited to 'man')
| -rw-r--r-- | man/cryptsetup.8 | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/man/cryptsetup.8 b/man/cryptsetup.8 index 05ee1b7a..e8592a62 100644 --- a/man/cryptsetup.8 +++ b/man/cryptsetup.8 @@ -1722,7 +1722,10 @@ and for authentication). Both these keys are stored in one LUKS keyslot. \fBWARNING:\fR All support for authenticated modes is experimental and there are only some modes available for now. Note that there are a very few authenticated encryption algorithms that are suitable -for disk encryption. +for disk encryption. You also cannot use CRC32 or any other non-cryptographic +checksums (other than the special integrity mode "none"). If for some reason +you want to have integrity control without using authentication mode, then you +should separately configure dm-integrity independently of LUKS2. .SH NOTES ON LOOPBACK DEVICE USE Cryptsetup is usually used directly on a block device (disk |