From 541bb017d2eb940f7f56a6cf79ba0dacf8766ba3 Mon Sep 17 00:00:00 2001
From: Werner Koch <wk@gnupg.org>
Date: Thu, 22 Jul 1999 18:11:55 +0000
Subject: See ChangeLog: Thu Jul 22 20:03:03 CEST 1999  Werner Koch

---
 doc/gpg.sgml | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

(limited to 'doc')

diff --git a/doc/gpg.sgml b/doc/gpg.sgml
index 2c73715ae..344cefc67 100644
--- a/doc/gpg.sgml
+++ b/doc/gpg.sgml
@@ -696,6 +696,13 @@ Assume "yes" on most questions.
  Assume "no" on most questions.
 </para></listitem></varlistentry>
 
+<varlistentry>
+<term>--always-trust</term>
+<listitem><para>
+Skip key validation and assume that used keys are always fully trusted.
+You won't use this unless you have installed some external validation scheme.
+</para></listitem></varlistentry>
+
 
 <varlistentry>
 <term>--keyserver &ParmName;</term>
@@ -1094,6 +1101,17 @@ code.  This is always used with the newer cipher (those
 with a blocksize greater than 64 bit).
 </para></listitem></varlistentry>
 
+<varlistentry>
+<term>--allow-non-self-signed-uid</term>
+<listitem><para>
+Allow the import of keys with user IDs which are not self-signed.
+This is only allows the import - key validation will fail und you
+have to check the validity of the key my other means.  This hack is
+needed for some German keys generated with pgp 2.6.3in. You should really
+avoid using it, because OpenPGP has better mechanics to do separate signing
+and encryption keys.
+</para></listitem></varlistentry>
+
 
 <varlistentry>
 <term>--lock-once</term>
-- 
cgit v1.2.3