This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
This article is within the scope of WikiProject Cryptography, a collaborative effort to improve the coverage of Cryptography on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
[quote]The "cryptsetup" command-line interface does not write any headers to the encrypted volume, and hence only provides the bare essentials: Encryption settings have to be provided every time the disk is mounted (although usually employed with automated scripts), and only one key can be used per volume; the symmetric encryption key directly derived from the supplied passphrase. For these reasons, the use of cryptsetup is discouraged with plain passphrases. However, the simplicity of cryptsetup makes it useful when combined with third party software, for example, with smart card authentication.[/quote]
Here the author of this article confused "cryptsetup" with "cryptoloop". Please somebody fix that. --188.8.131.52 (talk) 01:32, 13 January 2011 (UTC)
I have just done that. This is my first edit so please tell if I'm doing something wrong. JackMateBaker (talk) 16:35, 4 February 2015 (UTC)
This seems fine to me - cryptsetup does have these weaknesses Tdk at squte (talk) 10:51, 5 February 2015 (UTC)
Tomb is a popular wrapper of dm-crypt using cryptsetup https://www.dyne.org/software/tomb It is a minimalist script adding more features for key handling and usability in application space. Shouldn't it be added here? JackMateBaker (talk) 16:49, 4 February 2015 (UTC)