security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2024-06-10 23:49:50 +02:00
Code Activity

* gpg.sgml: Document "tsign", clarify "setpref", clarify --recipient,

Browse Source 
document --hidden-recipient, document --hidden-encrypt-to, clarify
--no-encrypt-to, clarify --throw-keyid, document --no-throw-keyid.
This commit is contained in:
David Shaw 2002-11-03 13:40:39 +00:00
parent 06285e37b1
commit 1b593c0515
2 changed files with 50 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/ChangeLog
View File

@ -1,3 +1,10 @@
2002-11-03 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: Document "tsign", clarify "setpref", clarify
--recipient, document --hidden-recipient, document
--hidden-encrypt-to, clarify --no-encrypt-to, clarify
--throw-keyid, document --no-throw-keyid.
2002-10-24 David Shaw <dshaw@jabberwocky.com> 2002-10-24 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: Document --refresh-keys. * gpg.sgml: Document --refresh-keys.

51
doc/gpg.sgml
View File

@ -310,6 +310,14 @@ therefore never be revoked.</para></listitem></varlistentry>
Combines the functionality of nrsign and lsign to make a signature Combines the functionality of nrsign and lsign to make a signature
that is both non-revocable and that is both non-revocable and
non-exportable.</para></listitem></varlistentry> non-exportable.</para></listitem></varlistentry>
<varlistentry>
<term>tsign</term>
<listitem><para>
Make a trust signature. This is a signature that combines the notions
of certification (like a regular signature), and trust (like the
"trust" command). It is generally only useful in distinct communities
or groups.
</para></listitem></varlistentry>
<varlistentry> <varlistentry>
<term>revsig</term> <term>revsig</term>
<listitem><para> <listitem><para>
@ -419,7 +427,7 @@ are not already included in the preference list.
Set the list of user ID preferences to &ParmString;, this should be a Set the list of user ID preferences to &ParmString;, this should be a
string similar to the one printed by "pref". Using an empty string string similar to the one printed by "pref". Using an empty string
will set the default preference string, using "none" will set the will set the default preference string, using "none" will set the
preferences to nil. Use "gpg -v --version" to get a list of available preferences to nil. Use "gpg --version" to get a list of available
algorithms. This command just initializes an internal list and does algorithms. This command just initializes an internal list and does
not change anything unless another command (such as "updpref") which not change anything unless another command (such as "updpref") which
changes the self-signatures is used. changes the self-signatures is used.
@ -775,8 +783,20 @@ found in the secret keyring.
<term>-r, --recipient &ParmName;</term> <term>-r, --recipient &ParmName;</term>
<term></term> <term></term>
<listitem><para> <listitem><para>
Encrypt for user id &ParmName;. If this option is not Encrypt for user id &ParmName;. If this option or --hidden-recipient
specified, GnuPG asks for the user-id unless --default-recipient is given is not specified, GnuPG asks for the user-id unless
--default-recipient is given.
</para></listitem></varlistentry>
<varlistentry>
<term>-R, --hidden-recipient &ParmName;</term>
<term></term>
<listitem><para>
Encrypt for user id &ParmName;, but hide the keyid of the key. This
option hides the receiver of the message and is a countermeasure
against traffic analysis. If this option or --recipient is not
specified, GnuPG asks for the user-id unless --default-recipient is
given.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry> <varlistentry>
@ -813,11 +833,21 @@ No trust checking is performed for these user ids and
even disabled keys can be used. even disabled keys can be used.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry>
<term>--hidden-encrypt-to &ParmName;</term>
<listitem><para>
Same as --hidden-recipient but this one is intended for use in the
options file and may be used with your own user-id as a hidden
"encrypt-to-self". These keys are only used when there are other
recipients given either by use of --recipient or by the asked user id.
No trust checking is performed for these user ids and even disabled
keys can be used.
</para></listitem></varlistentry>
<varlistentry> <varlistentry>
<term>--no-encrypt-to</term> <term>--no-encrypt-to</term>
<listitem><para> <listitem><para>
Disable the use of all --encrypt-to keys. Disable the use of all --encrypt-to and --hidden-encrypt-to keys.
</para></listitem></varlistentry> </para></listitem></varlistentry>
@ -1626,12 +1656,17 @@ Resets the --auto-check-trustdb option.
<varlistentry> <varlistentry>
<term>--throw-keyid</term> <term>--throw-keyid</term>
<listitem><para> <listitem><para>
Do not put the keyid into encrypted packets. This option Do not put the keyids into encrypted packets. This option hides the
hides the receiver of the message and is a countermeasure receiver of the message and is a countermeasure against traffic
against traffic analysis. It may slow down the decryption analysis. It may slow down the decryption process because all
process because all available secret keys are tried. available secret keys are tried.
</para></listitem></varlistentry> </para></listitem></varlistentry>
<varlistentry>
<term>--no-throw-keyid</term>
<listitem><para>
Resets the --throw-keyid option.
</para></listitem></varlistentry>
<varlistentry> <varlistentry>
<term>--not-dash-escaped</term> <term>--not-dash-escaped</term>