security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-01-03 12:11:33 +01:00
Code Activity

* debugging.texi (Common Problems): Add a note about corrupted

Browse Source 
keys in --search-keys.
This commit is contained in:
Werner Koch 2009-07-06 21:33:34 +00:00
parent 81972ca7d5
commit 58e6e28bb1
2 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/ChangeLog
View File

@ -1,3 +1,8 @@
2009-07-06 Werner Koch <wk@g10code.com>
* debugging.texi (Common Problems): Add a note about corrupted
keys in --search-keys.
2009-06-02 Werner Koch <wk@g10code.com>
* tools.texi (watchgnupg): Typo fix. Fixes bug#1065.

9
doc/debugging.texi
View File

@ -228,6 +228,15 @@ instead of @command{wine}, which will launch a windows console that
implements those additional features.
@item Why does GPG's --search-key list weird keys?
For performance reasons the keyservers do not check the keys the same
way @command{gpg} does. It may happen that the listing of keys
available on the keyservers shows keys with wrong user IDs or with user
Ids from other keys. If you try to import this key, the bad keys or bad
user ids won't get imported, though. This is a bit unfortunate but we
can't do anything about it without actually downloading the keys.
@end itemize