eessppeelllloo/cryptsetup
1
0
Fork 0
mirror of https://gitlab.com/cryptsetup/cryptsetup.git synced 2025-12-16 13:20:11 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add a note about CRC32 and other non-cryptographic checksums

Browse Source
This commit is contained in:
Your Name
2021-05-11 00:07:36 +03:00
committed by Milan Broz
parent db44e9de22
commit 5776c52bcf
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
man/cryptsetup.8
View File

@@ -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 \fBWARNING:\fR All support for authenticated modes is experimental
and there are only some modes available for now. Note that there and there are only some modes available for now. Note that there
are a very few authenticated encryption algorithms that are suitable 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 .SH NOTES ON LOOPBACK DEVICE USE
Cryptsetup is usually used directly on a block device (disk Cryptsetup is usually used directly on a block device (disk