Llewellyn/Tomb
1
0
Fork 0
mirror of https://github.com/Llewellynvdm/Tomb.git synced 2024-12-31 13:12:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

documentation fix for default xts cipher string

Browse Source
This commit is contained in:
Jaromil 2019-11-18 10:17:38 +01:00
parent 377e335e93
commit e9fd1a19e1
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/tomb.1
View File

@ -61,7 +61,7 @@ option \fI-k\fR should be used to specify a key file; in case of
encryption to GPG recipients the \fI-g\fR flag should be used followed
by \fI-r\fR and the recipient's secret GPG key id. The \fI-o\fR
option can be used to specify the cipher specification: default is
"aes-xts-plain64:sha256", old versions of Tomb used
"aes-xts-plain64", old versions of Tomb used
"aes-cbc-essiv:sha256". If you are looking for something exotic, also
try "serpent-xts-plain64". More options may be found in cryptsetup(8)
and Linux documentation. This operation requires root privileges to
@ -242,7 +242,7 @@ of the default \fIrw,noatime,nodev\fR, i.e. to mount a tomb read-only
(ro) to prevent any modification of its data. Can also be used to
change the symmetric encryption algorithm for keys during \fIforge\fR
operations (default \fIAES256\fR) or the LUKS encryption method during
\fIlock\fR operations (default \fIaes-xts-plain64:sha256\fR).
\fIlock\fR operations (default \fIaes-xts-plain64\fR).
.B
.IP "-f"
Force flag, currently used to override swap checks, might be

2
tomb
View File

@ -2016,7 +2016,7 @@ forge_key() {
#
# Lock the given tomb with the given key file, in fact formatting the
# loopback volume as a LUKS device.
# Default cipher 'aes-xts-plain64:sha256'can be overridden with -o
# Default cipher 'aes-xts-plain64'can be overridden with -o
lock_tomb_with_key() {
# old default was aes-cbc-essiv:sha256
# Override with -o