On my F10 + 4.2 install I have a very recently created public keyring. I manually imported half a dozen signatures. Kgpg lists them, and KMail uses them. Everything seemed fine.
KMail is set to import signatures automatically. I've seen it import quite a few since then, and the messages report the status of the signature. However, those signatures are not seen by Kgpg - and never show up in the key management screen.
I've discussed this on the kde-pim list. I've talked to a kgpg developer. I've talked to a kmail developer. I've asked on IRC #kontact.
No-one seems to have any idea, other than the stock 'it must be fedora' :-)
Anne
On Thu, Feb 26, 2009 at 1:47 PM, Anne Wilson cannewilson@googlemail.com wrote:
On my F10 + 4.2 install I have a very recently created public keyring. I manually imported half a dozen signatures. Kgpg lists them, and KMail uses them. Everything seemed fine.
KMail is set to import signatures automatically. I've seen it import quite a few since then, and the messages report the status of the signature. However, those signatures are not seen by Kgpg - and never show up in the key management screen.
I've discussed this on the kde-pim list. I've talked to a kgpg developer. I've talked to a kmail developer. I've asked on IRC #kontact.
No-one seems to have any idea, other than the stock 'it must be fedora' :-)
Anne
As part of a class I tried to setup a gnupg and send an encrypted email. KGPG was helpful (even though I used the console) but couldn't get Kmail to properly encrypt with the receivers public key. Evolution wasn't as picky. This was on Centos 5.2 however.
But basically, if I had to randomly guess, I'd assume that Kmail was the problem.
On Thursday 26 February 2009 21:02:47 Arthur Pemberton wrote:
On Thu, Feb 26, 2009 at 1:47 PM, Anne Wilson cannewilson@googlemail.com
wrote:
On my F10 + 4.2 install I have a very recently created public keyring. I manually imported half a dozen signatures. Kgpg lists them, and KMail uses them. Everything seemed fine.
KMail is set to import signatures automatically. I've seen it import quite a few since then, and the messages report the status of the signature. However, those signatures are not seen by Kgpg - and never show up in the key management screen.
I've discussed this on the kde-pim list. I've talked to a kgpg developer. I've talked to a kmail developer. I've asked on IRC #kontact.
No-one seems to have any idea, other than the stock 'it must be fedora' :-)
Anne
As part of a class I tried to setup a gnupg and send an encrypted email. KGPG was helpful (even though I used the console) but couldn't get Kmail to properly encrypt with the receivers public key. Evolution wasn't as picky. This was on Centos 5.2 however.
KMail is signing and encrypting without any problem.
But basically, if I had to randomly guess, I'd assume that Kmail was the problem.
You can't. Neither the KMail devs nor the Kgpg ones know what's happening. A kubuntu user is running kde 4.2 and kgpg is working correctly for him, but that's the only thing I've managed to tie down.
Anne
Anne Wilson wrote:
On Thursday 26 February 2009 21:02:47 Arthur Pemberton wrote:
On Thu, Feb 26, 2009 at 1:47 PM, Anne Wilson cannewilson@googlemail.com
wrote:
On my F10 + 4.2 install I have a very recently created public keyring. I manually imported half a dozen signatures. Kgpg lists them, and KMail uses them. Everything seemed fine.
KMail is set to import signatures automatically. I've seen it import quite a few since then, and the messages report the status of the signature. However, those signatures are not seen by Kgpg - and never show up in the key management screen.
I've discussed this on the kde-pim list. I've talked to a kgpg developer. I've talked to a kmail developer. I've asked on IRC #kontact.
No-one seems to have any idea, other than the stock 'it must be fedora' :-)
Anne
As part of a class I tried to setup a gnupg and send an encrypted email. KGPG was helpful (even though I used the console) but couldn't get Kmail to properly encrypt with the receivers public key. Evolution wasn't as picky. This was on Centos 5.2 however.
KMail is signing and encrypting without any problem.
But basically, if I had to randomly guess, I'd assume that Kmail was the problem.
You can't. Neither the KMail devs nor the Kgpg ones know what's happening. A kubuntu user is running kde 4.2 and kgpg is working correctly for him, but that's the only thing I've managed to tie down.
rpm -q gnupg2 gnupg
Fedora's gpgme defaults to using gnupg2(/usr/bin/gpg2), maybe some parts of kmail/kgpg still depend on gnupg(1) somehow?
-- Rex
On Thursday 26 February 2009 21:41:02 Rex Dieter wrote:
rpm -q gnupg2 gnupg
Fedora's gpgme defaults to using gnupg2(/usr/bin/gpg2), maybe some parts of kmail/kgpg still depend on gnupg(1) somehow?
gnupg2-2.0.9-3.fc10.i386 gnupg-1.4.9-4.fc10.i386
Mandriva uses the same gnupg2-2.0.9-3 but a slightly different version of gnupg - 1.4.9-5.
Anne
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Anne Wilson wrote:
KMail is signing and encrypting without any problem.
Are you using as part of Kontact or stand-alone? I've seen problems with KMail signing when in Kontact, but worked fine outside of it.
- --Ben
On Friday 27 February 2009 02:16:08 Ben Boeckel wrote:
Anne Wilson wrote:
KMail is signing and encrypting without any problem.
Are you using as part of Kontact or stand-alone? I've seen problems with KMail signing when in Kontact, but worked fine outside of it.
Inside Kontact. As I said, it signs and encrypts. The problem is in getting signatures to display in kgpg.
Anne
-
Anne Wilson -
Arthur Pemberton -
Ben Boeckel -
Rex Dieter