mirror of
https://gitlab.com/cryptsetup/cryptsetup.git
synced 2025-12-14 20:30:04 +01:00
Mispelling fixes.
git-svn-id: https://cryptsetup.googlecode.com/svn/trunk@468 36d66b0a-2a48-0410-832c-cd162a569da5
This commit is contained in:
@@ -8,7 +8,7 @@ Important changes
|
|||||||
* Several userspace crypto backends support
|
* Several userspace crypto backends support
|
||||||
|
|
||||||
cryptsetup now supports generic crypto backend interface which allows
|
cryptsetup now supports generic crypto backend interface which allows
|
||||||
compile package with various crypto library, these are already implemented:
|
compile package with various crypto libraries, these are already implemented:
|
||||||
|
|
||||||
* gcrypt (default, used in previous versions)
|
* gcrypt (default, used in previous versions)
|
||||||
* OpenSSL
|
* OpenSSL
|
||||||
@@ -65,7 +65,7 @@ Important changes
|
|||||||
|
|
||||||
Please note that loopAES dm-crypt mode is provided for compatibility reasons
|
Please note that loopAES dm-crypt mode is provided for compatibility reasons
|
||||||
(so you do not need to patch kernel and util-linux to map existing volumes)
|
(so you do not need to patch kernel and util-linux to map existing volumes)
|
||||||
but is is not, and never will be, optimized for speed.
|
but it is not, and never will be, optimized for speed.
|
||||||
It is experimental feature for now.
|
It is experimental feature for now.
|
||||||
|
|
||||||
* WARNING: This is the last cryptsetup release which supports library with
|
* WARNING: This is the last cryptsetup release which supports library with
|
||||||
@@ -78,7 +78,7 @@ Other changes
|
|||||||
~~~~~~~~~~~~~
|
~~~~~~~~~~~~~
|
||||||
* Increase libcryptsetup version (loopAES change), still fully backward compatible.
|
* Increase libcryptsetup version (loopAES change), still fully backward compatible.
|
||||||
* Fixes static build (--disable-static-cryptsetup now works properly).
|
* Fixes static build (--disable-static-cryptsetup now works properly).
|
||||||
* Supports secure data flag for device-mapper iotcl (will be in 2.6.39,
|
* Supports secure data flag for device-mapper ioctl (will be in 2.6.39,
|
||||||
forcing kernel to wipe all ioctl buffers with possible key data).
|
forcing kernel to wipe all ioctl buffers with possible key data).
|
||||||
To enable this flag you need new device-mapper library, in LVM2 2.02.84.
|
To enable this flag you need new device-mapper library, in LVM2 2.02.84.
|
||||||
* Add copyright texts into some files and adds GPL exception allowing
|
* Add copyright texts into some files and adds GPL exception allowing
|
||||||
|
|||||||
@@ -150,7 +150,7 @@ For more information about LUKS, see \fBhttp://code.google.com/p/cryptsetup/wiki
|
|||||||
|
|
||||||
.SH loop-AES EXTENSION
|
.SH loop-AES EXTENSION
|
||||||
|
|
||||||
cryptsetup allows to map loop-AES encrypted partition using compatible dm-crypt mode.
|
cryptsetup supports mapping of loop-AES encrypted partition using compatible dm-crypt mode.
|
||||||
|
|
||||||
.PP
|
.PP
|
||||||
\fIloopaesOpen\fR <device> <name> \-\-key-file <keyfile>
|
\fIloopaesOpen\fR <device> <name> \-\-key-file <keyfile>
|
||||||
@@ -246,7 +246,7 @@ For \fIluksFormat\fR it defines which kernel random number generator will be use
|
|||||||
See \fBNOTES ON RNG\fR for more information. Use \fIcryptsetup \-\-help\fR to show default RNG.
|
See \fBNOTES ON RNG\fR for more information. Use \fIcryptsetup \-\-help\fR to show default RNG.
|
||||||
.TP
|
.TP
|
||||||
.B "\-\-key-slot, \-S"
|
.B "\-\-key-slot, \-S"
|
||||||
For LUKS operations that add key material, this options allows to you specify which key slot is selected for the new key. This option can be used for \fIluksFormat\fR and \fIluksAddKey\fR.
|
For LUKS operations that add key material, this options allows you to specify which key slot is selected for the new key. This option can be used for \fIluksFormat\fR and \fIluksAddKey\fR.
|
||||||
.TP
|
.TP
|
||||||
.B "\-\-key-size, \-s"
|
.B "\-\-key-size, \-s"
|
||||||
set key size in bits.
|
set key size in bits.
|
||||||
|
|||||||
Reference in New Issue
Block a user