From 9299f3eecf08a6a877c37968ddf704d701f9a6a3 Mon Sep 17 00:00:00 2001
From: Jaromil <jaromil@dyne.org>
Date: Wed, 20 Feb 2019 20:36:26 +0100
Subject: [PATCH] mention need of using trusted gpg keys in manpage

documentation to address issue #340
---
 doc/tomb.1 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/tomb.1 b/doc/tomb.1
index 4806906..4c9c271 100644
--- a/doc/tomb.1
+++ b/doc/tomb.1
@@ -238,7 +238,8 @@ symmetric passphrase to protect a tomb key. This option can be followed by \fI-r
 .B
 .IP "-r \fI<gpg_id>[,<gpg_id2>]\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
 .IP "--kdf \fI<itertime>\fR"
 Activate the KDF feature against dictionary attacks when creating a