mirror of
https://github.com/Llewellynvdm/Tomb.git
synced 2024-09-28 20:59:02 +00:00
mention need of using trusted gpg keys in manpage
documentation to address issue #340
This commit is contained in:
parent
12767764fb
commit
9299f3eecf
@ -238,7 +238,8 @@ symmetric passphrase to protect a tomb key. This option can be followed by \fI-r
|
|||||||
.B
|
.B
|
||||||
.IP "-r \fI<gpg_id>[,<gpg_id2>]\fR"
|
.IP "-r \fI<gpg_id>[,<gpg_id2>]\fR"
|
||||||
Provide a new set of recipient(s) to encrypt a tomb key. \fIgpg_ids\fR
|
Provide a new set of recipient(s) to encrypt a tomb key. \fIgpg_ids\fR
|
||||||
can be one or more GPG key ID, comma separated.
|
can be one or more GPG key ID, comma separated. All GPG keys must be
|
||||||
|
trusted keys in GPG.
|
||||||
.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
|
||||||
|
Loading…
Reference in New Issue
Block a user