security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-22 10:19:57 +01:00
Code Activity

* gpg.sgml: Clarify --min-cert-level a bit.

Browse Source
This commit is contained in:
David Shaw 2005-05-05 12:39:36 +00:00
parent d9d902dffb
commit cf7c0feca4
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/ChangeLog
View File

@ -1,3 +1,7 @@
2005-05-05 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: Clarify --min-cert-level a bit.
2005-03-14 Werner Koch <wk@g10code.com>
* gnupg-w32.reg: Removed.

10
doc/gpg.sgml
View File

@ -1112,10 +1112,10 @@ This option defaults to 0 (no particular claim).
<varlistentry>
<term>--min-cert-level</term>
<listitem><para>
When building the trust database, disregard any signatures with a
certification level below this. Defaults to 2, which disregards level
1 signatures. Note that level 0 "no particular claim" signatures are
always accepted.
When building the trust database, treat any signatures with a
certification level below this as invalid. Defaults to 2, which
disregards level 1 signatures. Note that level 0 "no particular
claim" signatures are always accepted.
</para></listitem></varlistentry>
@ -1771,7 +1771,7 @@ not to use a comment string. --comment may be repeated multiple times
to get multiple comment strings. --no-comments removes all comments.
It is a good idea to keep the length of a single comment below 60
characters to avoid problems with mail programs wrapping such lines.
Note, that those comment lines, like all other header lines, are not
Note that comment lines, like all other header lines, are not
protected by the signature.
</para></listitem></varlistentry>