1 |
Add the following lines to ~/.gnupg/gpg.conf: |
2 |
|
3 |
keyserver x-hkp://pgp.mit.edu |
4 |
keyserver-options auto-key-retrieve include-disabled include-revoked \ |
5 |
honor-keyserver-url |
6 |
|
7 |
(Except don't break the line in your conf) |
8 |
|
9 |
The keyserver-option "auto-key-retrieve" tells gpg to try to get a key |
10 |
from a keyserver whenever it's verifying a message but lacks the public |
11 |
key on your keyring. |
12 |
|
13 |
You can check 'man gpg' for more information about tweaking gpg's |
14 |
behavior, but the options above will probably be just fine for your use. |
15 |
|
16 |
-Chris |
17 |
|
18 |
|
19 |
On 17:33 Sat 18 Feb , Rafael Bugajewski wrote: |
20 |
> Hi all, |
21 |
> |
22 |
> I have a problem with KMail regarding the GnuPG plugin. I think i just do not |
23 |
> know how to use it and where to find documentation, so a little help would be |
24 |
> useful. |
25 |
> |
26 |
> The plugin itself works fine, I can send encrypted and signed messages, I get |
27 |
> always a prompt in which I can enter my passphrase etc. |
28 |
> |
29 |
> My only problem is if I receive signed messages from unknown identities. KMail |
30 |
> puts the whole message into a yellow box and says that there is a unknown |
31 |
> key. There is no possibility to search for the key and insert it, or is it |
32 |
> and I do not know about it? It would be nice to add new keys directly from |
33 |
> the KMail interface. If it is not possible, what is the fastest _and_ most |
34 |
> user friendly way? |
35 |
> |
36 |
> Greets, |
37 |
> |
38 |
> Rafael Bugajewski |
39 |
|
40 |
|
41 |
|
42 |
-- |
43 |
Christopher Cowart |
44 |
Unix Systems Administrator |
45 |
Residential Computing, UC Berkeley |
46 |
"May all your pushes be popped" |