better documentation for kdf

also correctly use _failure on fatal error using --kdf
This commit is contained in:
Jaromil 2016-11-18 13:54:18 +01:00
parent c502ef3d92
commit fa44f46eba
2 changed files with 6 additions and 6 deletions

View File

@ -201,10 +201,10 @@ the \fIsize\fR of the new file to be created. Units are megabytes (MiB).
.B .B
.IP "--kdf \fI<itertime>\fR" .IP "--kdf \fI<itertime>\fR"
Activate the KDF feature against dictionary attacks when creating a Activate the KDF feature against dictionary attacks when creating a
key: forces a delay of \fI<itertime>\fR seconds every time this key is used. key: forces a delay of \fI<itertime>\fR times every time this key is
You should keep in mind that the actual iteration count is calculated based on used. The actual time to wait depends on the CPU speed of the
the performance of the computer where you forge the key. computer where the key is used. Using 5 or 10 is a sane amount for
The argument must be an integer, so you cannot say \fI--kdf 0.3\fR for 300ms. modern computers, the value is multiplied by 1 million.
.B .B
.IP "-h" .IP "-h"
Display a help text and quit. Display a help text and quit.

4
tomb
View File

@ -1148,8 +1148,8 @@ gen_key() {
if [[ "$itertime" != <-> ]]; then if [[ "$itertime" != <-> ]]; then
unset tombpass unset tombpass
unset tombpasstmp unset tombpasstmp
_error "Wrong argument for --kdf: must be an integer number (iteration seconds)." _warning "Wrong argument for --kdf: must be an integer number (iteration seconds)."
_error "Depending on the speed of machines using this tomb, use 1 to 10, or more" _failure "Depending on the speed of machines using this tomb, use 1 to 10, or more"
return 1 return 1
fi fi
# --kdf takes one parameter: iter time (on present machine) in seconds # --kdf takes one parameter: iter time (on present machine) in seconds