Re: Relationship between kmail and kgpg

On Sunday 01 March 2009 03:18:53 Emanoil Kotsev wrote:
> Anne Wilson wrote:
> > KMail appears to be pulling in new signatures.   However, the only ones
> > that
> > show up in kgpg are those that I imported manually.  This implies, to me,
> > that
> > kmail is using a different keyring from gpg.  Comments?
> >
> > Anne
>
> you should check about gpg-agent
>
> ps -fu `id -un` | grep gpg
> emanoil   6862  6806  0 Feb26 ?
> 00:00:00 /usr/bin/ssh-agent /usr/bin/gpg-agent --daemon --sh
> --write-env-file=/home/emanoil/.gnupg/gpg-agent-info-maistor
> /usr/bin/dbus-launch --exit-with-session /usr/bin/keytouchd-launch
> /usr/bin/startkde emanoil   6863  6806  0 Feb26 ?
> 00:00:07 /usr/bin/gpg-agent --daemon --sh
> --write-env-file=/home/emanoil/.gnupg/gpg-agent-info-maistor
> /usr/bin/dbus-launch --exit-with-session /usr/bin/keytouchd-launch
> /usr/bin/startkde emanoil   6984     1  0 Feb26 ?        00:00:00 kgpg
> -session
> 10e1d0db73000122637470600000069520026_1235636586_910379
> emanoil  25512 24303  0 04:14 pts/8    00:00:00 grep gpg
>
I have a much shorter list:

ps -fu `id -un` | grep gpg
anne      2871     1  0 11:05 ?        00:00:00 /usr/bin/gpg-agent -s --daemon
anne      2989     1  0 11:06 ?        00:00:01 kgpg -session 
104141310000123427948300000056040013_1234811693_685431
anne      3345  3257  0 11:13 pts/1    00:00:00 grep gpg

>
> man gpg-agent
>
> check also
>
> ~/.gnupg/gpg-agent.conf
>
> perhaps it helps you
>
All checked.  The config files are exactly the same as on other boxes where I 
don't see the problem.

> for me kmail uses exatcly the keys from the .gnupg keyring file
>
> it's working just fine
>
Yes, kmail seems to be working fine.  Kgpg also does whatever I ask it to.  It 
also adds to its management page any keys that I import either through kgpg or 
the CLI.  What it doesn't do is display the keys that kmail has automatically 
imported.  This is a problem I'm only seeing on this one, Fedora10, 
installation.

Hmm - just realised that many recent message have the following:

Message was signed on 02/02/2009 01:43 with unknown key 0xsomething.
The validity of the signature cannot be verified.
Status: No public key to verify the signature

I guess that kmail is not respecting the setting to import the signatures, if 
all recent 'new' sigs are like this.  Maybe that's a packaging bug that needs 
to be reported.

Funny how an unrelated suggestion can cause us to break the circle of thinking 
:-)

Anne

_______________________________________________
KDE PIM users mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkmqcR8ACgkQbMErw/n0TZoMxQCcC5F3VacMDvOM2wd11btD3AHB
bq0AmwS7xHFgUEBlP9khxAAuhtaNDsPt
=iJHO
-----END PGP SIGNATURE-----