diff options
| author | Werner Koch <wk@gnupg.org> | 2009-07-06 23:33:34 +0200 |
|---|---|---|
| committer | Werner Koch <wk@gnupg.org> | 2009-07-06 23:33:34 +0200 |
| commit | 58e6e28bb1e955eaac7307bbcc20319383b79c23 (patch) | |
| tree | 9e98ab2c96f2b4da1cec14711a6cf1d9c12b45cf /doc/debugging.texi | |
| parent | Create a pkcs#10 request directly from a card. (diff) | |
| download | gnupg2-58e6e28bb1e955eaac7307bbcc20319383b79c23.tar.xz gnupg2-58e6e28bb1e955eaac7307bbcc20319383b79c23.zip | |
* debugging.texi (Common Problems): Add a note about corrupted
keys in --search-keys.
Diffstat (limited to '')
| -rw-r--r-- | doc/debugging.texi | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/debugging.texi b/doc/debugging.texi index f88f69372..a7991611d 100644 --- a/doc/debugging.texi +++ b/doc/debugging.texi @@ -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 |