gpg and kmail...something wrong
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hiya gang, I've seen quite a few posts in the list that were signed with gpg (or pgp I guess). Some just have a simple, short yellow line letting me know that I don't have this key on my keyring. Others though, have a big fat yellow line with the following in it: Message was signed with unknown key. The validity of the signature cannot be verified. Problem: OpenPGP plug-in was not specified. Use the 'Settings->Configure KMail->Security' dialog to specify the plug-in or ask your system administrator to do that for you. Okay, no problem. I go into the security setup part in kmail, found the plugins in /usr/lib/cryptplug (containing:gpgme-openpgp.a, .la, .so and gpgme-smime.a, .la, .so). I highlighted gpgme-openpgp.so, and clicked the 'activate' button and an asterisk shows up next to it in the window affirming it's activated. I then click 'apply', and kmail crashes. Just disappears, and I have to click on the kmail icon to start it again. I did this with the gpgme-smime.so also, exactly as I did with the other, and when I click 'apply', it crashes kmail. I tried this with each of the six things in /usr/lib/cryptplug one at a time, and each one crashes kmail when I click 'apply'. I have two SuSE public keys on my keyring, and they show up green in an email. My own show up green. Others like I said, show up as they should if I don't have their public key, but many that I *do* have the public key of, show up with the big fat response I gave above. Is anyone else having the same problems trying to get a plugin thing to work in kmail (SuSE 8.2, patched everything that YOU said I needed)? Should I report this as a bug to someone (the kde team? the kmail team?...), or does someone have an idea what's happening and a way to fix it? Thanks for any help. Take care and be good. John - -- A butterfly is: Pretty,soft,harmless...and useless, just like M$N. My Penguin and my Gecko eat butterflies. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+zHAJH5oDXyLKXKQRAuTKAJ9mR1n+tMucvlC7wr+Km/w1H5RcsACggvDw 2U3cwLVw2BuIhMihemUPjoM= =nTBc -----END PGP SIGNATURE-----
I have looked into this situation myself, with another list where I was trying to collect the necessary keys from some friends, so we could have encryption and validation. Some of them use Evolution, some KMail, some Mozilla. Each one has their own method of attaching the *.asc key to the email message, therefore, I suspect it's not a "bug" in the normal sense, just a problem with the overall deployment concept of pgp/gpg enhanced emails. I haven't dug waist deep into it, since I didn't have the time, rather I just looked it over for about 2 days off and on, and decided that I can just live w/o it for now... The messages I get from someone in Evolution look/work perfectly (when I use Evolution) look/work broken like your description (when I used KMail) and I don't know what they do in Mozilla (didn't try it) The messages I get from someone using KMail/Mozilla appear the same in Evolution, and don't seem to get me anywhere, even when I've pulled down their key. The Evolution format has the basic ID string to plug in when searching for someone's key from the keyservers. It's very easy! I haven't quite figured out the same idea from one sent through the other MUAs. :( Like I said, I haven't gone too deep into this problem, but from my previous observations, it's just a non-compatibility between MUAs. I can't say why KMail is crashing... sorry! :( HTH, Travis. On Thu, 2003-05-22 at 01:36, John wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hiya gang,
I've seen quite a few posts in the list that were signed with gpg (or pgp I guess). Some just have a simple, short yellow line letting me know that I don't have this key on my keyring. Others though, have a big fat yellow line with the following in it:
Message was signed with unknown key. The validity of the signature cannot be verified. Problem: OpenPGP plug-in was not specified. Use the 'Settings->Configure KMail->Security' dialog to specify the plug-in or ask your system administrator to do that for you.
Okay, no problem. I go into the security setup part in kmail, found the plugins in /usr/lib/cryptplug (containing:gpgme-openpgp.a, .la, .so and gpgme-smime.a, .la, .so). I highlighted gpgme-openpgp.so, and clicked the 'activate' button and an asterisk shows up next to it in the window affirming it's activated. I then click 'apply', and kmail crashes. Just disappears, and I have to click on the kmail icon to start it again. I did this with the gpgme-smime.so also, exactly as I did with the other, and when I click 'apply', it crashes kmail. I tried this with each of the six things in /usr/lib/cryptplug one at a time, and each one crashes kmail when I click 'apply'. I have two SuSE public keys on my keyring, and they show up green in an email. My own show up green. Others like I said, show up as they should if I don't have their public key, but many that I *do* have the public key of, show up with the big fat response I gave above. Is anyone else having the same problems trying to get a plugin thing to work in kmail (SuSE 8.2, patched everything that YOU said I needed)? Should I report this as a bug to someone (the kde team? the kmail team?...), or does someone have an idea what's happening and a way to fix it? Thanks for any help. Take care and be good.
John - -- A butterfly is: Pretty,soft,harmless...and useless, just like M$N. My Penguin and my Gecko eat butterflies. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)
iD8DBQE+zHAJH5oDXyLKXKQRAuTKAJ9mR1n+tMucvlC7wr+Km/w1H5RcsACggvDw 2U3cwLVw2BuIhMihemUPjoM= =nTBc -----END PGP SIGNATURE----- -- Travis Owens
Linux MDs
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 22 May 2003 01:56, Travis Owens wrote:
I have looked into this situation myself, with another list where I was trying to collect the necessary keys from some friends, so we could have encryption and validation. Some of them use Evolution, some KMail, some Mozilla.
Each one has their own method of attaching the *.asc key to the email message, therefore, I suspect it's not a "bug" in the normal sense, just a problem with the overall deployment concept of pgp/gpg enhanced emails. I haven't dug waist deep into it, since I didn't have the time, rather I just looked it over for about 2 days off and on, and decided that I can just live w/o it for now...
<snip>
Travis.
I never had this problem in 7.3 or 8.0, since I never saw the message to use a 'plug-in' in any emails from this list or wherever, and I was using kgpg and/or gpa in 8.0 too. I sure do "hate to live w/out it", since it's a security thing and a privacy thing...neither of which should *ever* be taken complacently by *anyone* in this day and age (not slammin' you Travis, just voicin' an opinion, heh). Besides...what if I *needed* to be able to encrypt/decrypt these messages? So I still think it's a bug and related strongly to the kmail crashing (not that what I think really means much in this sense, LOL). I'd hate to send a bug report, but if there's no answers to this problem, then what else to do but either 'go backwards' and use 8.0, or let the kmail/kde folk know about it, is this reasoning correct or should I wait some more? John - -- A butterfly is: Pretty,soft,harmless...and useless, just like M$N. My Penguin and my Gecko eat butterflies. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+zNroH5oDXyLKXKQRAqWsAJ47xRiP6Hhy9XBXSRwr158JRcv0wQCgjhOY fAQmv/Kjg7IPSi7C9kUKY5M= =AVMg -----END PGP SIGNATURE-----
Hi, Am Donnerstag, 22. Mai 2003 08:36 schrieb John:
I've seen quite a few posts in the list that were signed with gpg (or pgp I guess).
Talking about signed e-mails on mailing lists: it realy doesn't make sense to sign your e-mails to a list unless you export your public key to one of the known key servers. If you don't know how, have a look at kgpg. It's simple enough. Either export your key to one of those key servers or just don't sign your mails to this list. Greetings from Bremen hartmut
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 22 May 2003 13:29, Hartmut Meyer wrote:
Hi,
Am Donnerstag, 22. Mai 2003 08:36 schrieb John:
I've seen quite a few posts in the list that were signed with gpg (or pgp I guess).
Talking about signed e-mails on mailing lists: it realy doesn't make sense to sign your e-mails to a list unless you export your public key to one of the known key servers.
If you don't know how, have a look at kgpg. It's simple enough.
Either export your key to one of those key servers or just don't sign your mails to this list.
Greetings from Bremen hartmut
It *is* doggonit! I already sent a post to the list earlier today saying I even put it on *another* keyserver that isn't even on kgpg's list! The least you could have done was checked more than one, or even told me what your message looks like in your mail client...does it have the big yellow line or the normal thin yellow line or what? You ain't helpin' me here at all with this post of yours. John - -- A butterfly is: Pretty,soft,harmless...and useless, just like M$N. My Penguin and my Gecko eat butterflies. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+zZeuH5oDXyLKXKQRAhrwAJ9PFDzuR2WS5tGD4m+1DbPJ5ECsqQCfaTdD 6hIMmRFV3o2GK9Aygqaq64A= =SxAy -----END PGP SIGNATURE-----
participants (3)
-
Hartmut Meyer
-
John
-
Travis Owens