security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-01-21 14:47:03 +01:00
Code Activity

Add a warning nite to --throw-keyds.

Browse Source
This commit is contained in:
Werner Koch 2008-08-28 14:57:25 +00:00
parent 2a7b21ac72
commit d92f06e882
2 changed files with 11 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/DETAILS
View File

@ -60,8 +60,8 @@ record; gpg2 does this by default and the option is a dummy.
be marked as ultimately trusted.
For X.509 certificates an 'u' is used for a trusted root
certificates (i.e. for the truct anchor) and and 'f' for
all other validated certificates.
certificate (i.e. for the trust anchor) and an 'f' for all
other valid certificates.
3. Field: length of key in bits.

15
doc/gpg.texi
View File

@ -2264,12 +2264,15 @@ will still get disabled.
@item --throw-keyids
@itemx --no-throw-keyids
Do not put the recipient key IDs into encrypted messages. This helps
to hide the receivers of the message and is a limited countermeasure
against traffic analysis. On the receiving side, it may slow down the
decryption process because all available secret keys must be tried.
@option{--no-throw-keyids} disables this option. This option is essentially
the same as using @option{--hidden-recipient} for all recipients.
Do not put the recipient key IDs into encrypted messages. This helps to
hide the receivers of the message and is a limited countermeasure
against traffic analysis.@footnote{Using a little social engineering
anyone who is able to decrypt the message can check whether one of the
other recipients is the one he suspects.} On the receiving side, it may
slow down the decryption process because all available secret keys must
be tried. @option{--no-throw-keyids} disables this option. This option
is essentially the same as using @option{--hidden-recipient} for all
recipients.
@item --not-dash-escaped
This option changes the behavior of cleartext signatures