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

a second snapshot thsi day (1.0.4f)

Browse source
This commit is contained in:
Werner Koch 2001-03-27 18:13:44 +00:00
parent 70c4c054cd
commit f0b82cd352
26 changed files with 1798 additions and 1744 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/ChangeLog
View file

@ -1,3 +1,7 @@
2001-03-27 Werner Koch <wk@gnupg.org>
* gpg.sgml: Add --no-sig-cache and --no-sig-create-check.
2001-03-23 Werner Koch <wk@gnupg.org>
* DETAILS: New status UNEXPECTED.

22
doc/gpg.sgml
View file

@ -1105,6 +1105,28 @@ The given name will not be checked so that a later loaded algorithm
will still get disabled.
</para></listitem></varlistentry>
<varlistentry>
<term>--no-sig-cache</term>
<listitem><para>
Does not not cache the verification status of key signatures.
Caching gives a much better performance in key listings, however if
you suspect that your public keyring is not saved against write
modifications, you can use this option to disable the caching. It
probably does not make sense to disable it because all kind of damange
can be done if someone else has write access to your public keyring.
</para></listitem></varlistentry>
<varlistentry>
<term>--no-sig-create-check</term>
<listitem><para>
GnuPG normally verifies each signature right after creation to protect
against bugs and hardware mal functions which could leak out bits from
the secret key. This extra verification needs some time (about 115%
fro DSA keys), and so this option can be used to disable it.
However, due to the fact that the signature creation needs manual
interaction, this performance penality does not matter in most setting.
</para></listitem></varlistentry>
<varlistentry>
<term>--throw-keyid</term>
<listitem><para>