mirror of
git://git.gnupg.org/gnupg.git
synced 2024-11-11 21:48:50 +01:00
* gpg.sgml: Add an example of what an exclamation mark is, as people seem
to miss it often.
This commit is contained in:
parent
c6f07b53b2
commit
e9fabace03
@ -1,3 +1,8 @@
|
|||||||
|
2003-12-21 David Shaw <dshaw@jabberwocky.com>
|
||||||
|
|
||||||
|
* gpg.sgml: Add an example of what an exclamation mark is, as
|
||||||
|
people seem to miss it often.
|
||||||
|
|
||||||
2003-12-07 David Shaw <dshaw@jabberwocky.com>
|
2003-12-07 David Shaw <dshaw@jabberwocky.com>
|
||||||
|
|
||||||
* gpg.sgml: Fix a few missing semicolons in & entities. Noted by
|
* gpg.sgml: Fix a few missing semicolons in & entities. Noted by
|
||||||
|
@ -1443,7 +1443,7 @@ must contain a '@' character. This is to help prevent pollution of
|
|||||||
the IETF reserved notation namespace. The --expert flag overrides the
|
the IETF reserved notation namespace. The --expert flag overrides the
|
||||||
'@' check. &ParmValue; may be any printable string; it will be
|
'@' check. &ParmValue; may be any printable string; it will be
|
||||||
encoded in UTF8, so you should check that your --charset is set
|
encoded in UTF8, so you should check that your --charset is set
|
||||||
correctly. If you prefix &ParmName; with an exclamation mark, the
|
correctly. If you prefix &ParmName; with an exclamation mark (!), the
|
||||||
notation data will be flagged as critical (rfc2440:5.2.3.15).
|
notation data will be flagged as critical (rfc2440:5.2.3.15).
|
||||||
--sig-notation sets a notation for data signatures. --cert-notation
|
--sig-notation sets a notation for data signatures. --cert-notation
|
||||||
sets a notation for key signatures (certifications). --set-notation
|
sets a notation for key signatures (certifications). --set-notation
|
||||||
@ -1480,8 +1480,8 @@ as well as when verifying a signature with a notation in it.
|
|||||||
<term>--set-policy-url &ParmString;</term>
|
<term>--set-policy-url &ParmString;</term>
|
||||||
<listitem><para>
|
<listitem><para>
|
||||||
Use &ParmString; as Policy URL for signatures (rfc2440:5.2.3.19). If
|
Use &ParmString; as Policy URL for signatures (rfc2440:5.2.3.19). If
|
||||||
you prefix it with an exclamation mark, the policy URL packet will be
|
you prefix it with an exclamation mark (!), the policy URL packet will
|
||||||
flagged as critical. --sig-policy-url sets a a policy url for data
|
be flagged as critical. --sig-policy-url sets a a policy url for data
|
||||||
signatures. --cert-policy-url sets a policy url for key signatures
|
signatures. --cert-policy-url sets a policy url for key signatures
|
||||||
(certifications). --set-policy-url sets both.
|
(certifications). --set-policy-url sets both.
|
||||||
</para><para>
|
</para><para>
|
||||||
@ -2361,7 +2361,7 @@ in front.
|
|||||||
</variablelist>
|
</variablelist>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Note that you can append an exclamation mark to key IDs or
|
Note that you can append an exclamation mark (!) to key IDs or
|
||||||
fingerprints. This flag tells GnuPG to use exactly the given primary
|
fingerprints. This flag tells GnuPG to use exactly the given primary
|
||||||
or secondary key and not to try to figure out which secondary or
|
or secondary key and not to try to figure out which secondary or
|
||||||
primary key to use.
|
primary key to use.
|
||||||
|
Loading…
Reference in New Issue
Block a user