Hello all. Just upgraded my SUSE 9.2 Pro system from kde-3.3 to 3.4. I use kmail for all my e-mail needs with integrated gpg for signing mail. I've never had any problems with gpg in the past. gpg-agent was set to start when I started my system and it would prompt me for my passphrase when I sent e-mail. However, now when I start my machine I get an error message about gpg-agent not running. Regardless of what I do, I cannot get gpg-agent to run correctly. And, when I send e-mail I get the following error message: You need a passphrase to unlock the secret key for user: (my key ID displayed here) Christopher Shanahan (N/A) This dialog will reappear every time the passphrase is needed. For a more secure solution that also allows caching the passphrase, use gpg-agent. gpg-agent was found in /usr/bin/gpg-agent, but does not appear to be running. For information on how to set up gpg-agent, see http://kmail.kde.org/kmail-pgpmime-howto.html I'm familiar with this howto and I just went through it again to make sure I didn't inadvertently break something. kmail seems to be setup correctly but I still cannot get my system to recognize gpg-agent as running. I used the following command, from the kmail-pgpmime-howto, to check gpg and it executed/finished without errors. cms@dl320:~/.gnupg> echo "test" | gpg -ase -r 0xA76872B8 | gpg You need a passphrase to unlock the secret key for user: "Christopher M. Shanahan (N/A) <cshanahan@comcast.net>" 1024-bit DSA key, ID A76872B8, created 2004-12-13 You need a passphrase to unlock the secret key for user: "Christopher M. Shanahan (N/A) <cshanahan@comcast.net>" 1024-bit ELG-E key, ID 9D972D71, created 2004-12-13 (main key ID A76872B8) gpg: encrypted with 1024-bit ELG-E key, ID 9D972D71, created 2004-12-13 "Christopher M. Shanahan (N/A) <cshanahan@comcast.net>" test gpg: Signature made Tue 22 Mar 2005 09:29:46 AM EST using DSA key ID A76872B8 gpg: Good signature from "Christopher M. Shanahan (N/A) <cshanahan@comcast.net>" Any ideas? I'm still reading but I thought I'd ask here, to speed things up. As always, TIA. Christopher Shanahan
Christopher, On Tuesday 22 March 2005 10:54, Christopher Shanahan wrote:
Hello all.
Just upgraded my SUSE 9.2 Pro system from kde-3.3 to 3.4. I use kmail for all my e-mail needs with integrated gpg for signing mail. I've never had any problems with gpg in the past. gpg-agent was set to start when I started my system and it would prompt me for my passphrase when I sent e-mail. However, now when I start my machine I get an error message about gpg-agent not running. Regardless of what I do, I cannot get gpg-agent to run correctly. And, when I send e-mail I get the following error message:
Is it possible that this is another manifestation of the missing dependencies in the newly supplied KDE packages that allow installation to proceed without all the required cyrus-sasl packages? It couldn't hurt to run YaST Install and Remove Software, search for packages that include "cyrus-sasl" and install all except the -devel package. Then see if your symptoms remain.
...
Christopher Shanahan
Randall Schulz
On Tuesday 22 March 2005 14:01, Randall R Schulz wrote:
Christopher,
On Tuesday 22 March 2005 10:54, Christopher Shanahan wrote:
Hello all.
Just upgraded my SUSE 9.2 Pro system from kde-3.3 to 3.4. I use kmail for all my e-mail needs with integrated gpg for signing mail. I've never had any problems with gpg in the past. gpg-agent was set to start when I started my system and it would prompt me for my passphrase when I sent e-mail. However, now when I start my machine I get an error message about gpg-agent not running. Regardless of what I do, I cannot get gpg-agent to run correctly. And, when I send e-mail I get the following error message:
Is it possible that this is another manifestation of the missing dependencies in the newly supplied KDE packages that allow installation to proceed without all the required cyrus-sasl packages?
It couldn't hurt to run YaST Install and Remove Software, search for packages that include "cyrus-sasl" and install all except the -devel package.
Then see if your symptoms remain.
Thank you for your thoughts, Randall. I have all the cyrus packages installed and I'm still having kmail/gpg problems. For example, when restarting my machine I get the following error message: The use of GnuPG Agent is enabled in GnuPG's configuration file (/home/cms/.gnupg/gpg.conf). However, the agent does not seem to be running. This could result in problems with signing/decryption. Please disable GnuPG Agent from KGpg settings, or fix the agent. Truth is, I'm not really sure if the problem deals specifically with kmail or gpg --or both. Thanks though. Christopher Shanahan
Christopher, On Tuesday 22 March 2005 11:35, Christopher Shanahan wrote:
...
Thank you for your thoughts, Randall. I have all the cyrus packages installed and I'm still having kmail/gpg problems. For example, when restarting my machine I get the following error message:
Well, it was just a hunch. Did you look in your ~/.xsession-errors log to see if there's anything there that might indicate in more detail what is going wrong?
...
Christopher Shanahan
Randall Schulz
On Tuesday 22 March 2005 14:53, Randall R Schulz wrote:
Christopher,
On Tuesday 22 March 2005 11:35, Christopher Shanahan wrote:
...
Thank you for your thoughts, Randall. I have all the cyrus packages installed and I'm still having kmail/gpg problems. For example, when restarting my machine I get the following error message:
Well, it was just a hunch.
Did you look in your ~/.xsession-errors log to see if there's anything there that might indicate in more detail what is going wrong?
Good idea, Randall. Found: kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf Off to Google... Thanks again, Randall Christopher Shanahan That's why this list --and most Linux lists-- is so great.
Your last two messages in this thread contain what appears to be a valid pgp signature. However, it does not seem to have been published, either on pgp.net or keyserver.net. According to the header information, both were written with kmail 1.8. Whatever problems do exist with your configuration, something does seem to be working.
On Wednesday 23 March 2005 04:42, Darryl Gregorash wrote:
Your last two messages in this thread contain what appears to be a valid pgp signature. However, it does not seem to have been published, either on pgp.net or keyserver.net. According to the header information, both were written with kmail 1.8. Whatever problems do exist with your configuration, something does seem to be working.
I have the same problem, and you will see that this message is signed too, because I typed in my passphrase (again). The problem is when you want to use gpg-agent (this will cache your private key, so you dont have to type in a passphrase every time you send an email). I definately have gpg-agent --daemon running, and it still does not realise this. I have all the symptoms described. Anyone have any luck discovering a fix? Cheers, H
On Tuesday 22 March 2005 23:42, Darryl Gregorash wrote:
Your last two messages in this thread contain what appears to be a valid pgp signature. However, it does not seem to have been published, either on pgp.net or keyserver.net. According to the header information, both were written with kmail 1.8. Whatever problems do exist with your configuration, something does seem to be working.
Yes, my mail seems to be getting signed correctly provided I input my passphrase when prompted to do so. I have no problem with that. However, I still get error messages related to gpg-agent, both when I send mail using kmail and when my system starts -- gpg-agent is set to start automatically -- even though gpg-agent is running. The problem seems to be some sort of conflict with openssl and one of the new kde packages, I just don't know which one. Too many packages depends on openssl for me to easily narrow the list of possible culprits. Of course, I could be way off base here; however, the error messages from .xsession-errors (thanks Randall) suggest to me that the problem deals with openssl since libcrypto.so.0.9.7 is provided by openssl. You tell me. Is the following error message saying the problem is related to openssl or some other kde/qt package? kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_conf kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf gpgmeplug checkMessageSignature status flags: 80 I've spent a fair amount of time searching the kde bug database but I cannot find any 'new' bugs for this issue as it relates to kde-3.4. I'll keep searching though. Again, thanks to all for their responses/hints. Christopher Shanahan
Christopher Shanahan wrote:
On Tuesday 22 March 2005 23:42, Darryl Gregorash wrote:
Your last two messages in this thread contain what appears to be a valid pgp signature. However, it does not seem to have been published....
Yes, my mail seems to be getting signed correctly provided I input my passphrase when prompted to do so. I have no problem with that. However, I
I'm not familiar with gpg-agent, since I'm using enigmail which seems to cache the password. Not that I've ever signed too many emails anyway :-)
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_conf kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf gpgmeplug checkMessageSignature status flags: 80
That certainly looks like errors in the libcrypto library, not kde or qt. There are some utils in the binutils package that may be able to dump the symbol table in that library for you, no idea what information they'll give you though. Check the manpages for nm and objdump, or see 'info binutils'.
The Wednesday 2005-03-23 at 12:45 -0600, Darryl Gregorash wrote:
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf gpgmeplug checkMessageSignature status flags: 80
That certainly looks like errors in the libcrypto library, not kde or qt. There are some utils in the binutils package that may be able to dump the symbol table in that library for you, no idea what information they'll give you though. Check the manpages for nm and objdump, or see 'info binutils'.
Which probably means that openssl*rpm needs to be updated too. -- Cheers, Carlos Robinson
On Wednesday 23 March 2005 18:07, Christopher Shanahan wrote:
On Tuesday 22 March 2005 23:42, Darryl Gregorash wrote:
Your last two messages in this thread contain what appears to be a valid pgp signature. However, it does not seem to have been published, either on pgp.net or keyserver.net. According to the header information, both were written with kmail 1.8. Whatever problems do exist with your configuration, something does seem to be working.
Yes, my mail seems to be getting signed correctly provided I input my passphrase when prompted to do so. I have no problem with that. However, I still get error messages related to gpg-agent, both when I send mail using kmail and when my system starts -- gpg-agent is set to start automatically -- even though gpg-agent is running. The problem seems to be some sort of conflict with openssl and one of the new kde packages, I just don't know which one. Too many packages depends on openssl for me to easily narrow the list of possible culprits.
Of course, I could be way off base here; however, the error messages from .xsession-errors (thanks Randall) suggest to me that the problem deals with openssl since libcrypto.so.0.9.7 is provided by openssl. You tell me. Is the following error message saying the problem is related to openssl or some other kde/qt package?
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: PKCS7_content_free kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_conf kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf gpgmeplug checkMessageSignature status flags: 80
I've spent a fair amount of time searching the kde bug database but I cannot find any 'new' bugs for this issue as it relates to kde-3.4. I'll keep searching though.
Again, thanks to all for their responses/hints.
Christopher Shanahan
Solved! I found that if I create a directory called env in ~/.kde and put in a shell script to start gpg-agent, it works perfectly (i found this by looking at startkde). So to fix: create a directory ~/.kde/env and put in this file: #!/bin/bash eval "$(gpg-agent --daemon)" Make it executable, and you are good to go, restart x, and it Just Works (TM) Now you can type in your GPG passphrase once, and it will be remembered for a while so you dont have to eg. type it in 6 times for replying to encrypted mail! It also stops kgpg complaining that the agent is not running. Hope that helps, H
participants (5)
-
Carlos E. R. -
Christopher Shanahan -
Darryl Gregorash -
Hamish -
Randall R Schulz