security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-03 22:56:33 +02:00
Code Activity

See ChangeLog: Thu Jul 22 20:03:03 CEST 1999 Werner Koch

Browse source
This commit is contained in:
Werner Koch 1999-07-22 18:11:55 +00:00
parent a316550579
commit 541bb017d2
14 changed files with 230 additions and 123 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/gpg.sgml
View file

@ -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>