I’m trying to run OSC on Arch Linux yet I keep getting this error:
/usr/lib/python2.7/site-packages/M2Crypto/__m2crypto.so: undefined symbol: SSLv2_method
M2Crypto is needed to access https://api.opensuse.org in a secure way.
Please install python-m2crypto.
whenever I try to make a commit (with
osc ci -m "Initial commit"
). python-m2crypto (specifically python2-m2crypto is) is installed so I haven’t the foggiest what the issue is. I have even tried upgrading python2-m2crypto to the latest version with:
sudo pip2 install --upgrade m2crypto
still I am getting this error (although the error does slightly change after running this, namely SSLv2 is replaced with SSLv3 in the above error message). Any ideas? I know this forum is mostly for openSUSE, but I have asked for help at the AUR OSC package’s description page with no reply and I thought you’s might have an idea. OSC is not generating errors when I add files with osc add, so its cause is alluding me.
Since I don’t use Arch at all,
Following is based on a bit of speculation, but I’ll walk you through the way I see your problem.
First, some light and quick reading suggests that Arch doesn’t distribute development headers (possibly including symbols) separately from the main package, so you’re not likely missing those in general.
So,
Then I’d take a look at what your package actually is.
You should know that SSL (and other types of encryption) everywhere had to patch and modify about 6 months (maybe up to 9 months or so) due to a number of discovered vulnerabilities… At least one which was specific to OpenSSL which has existed for close to two decades, and later a fundamental problem with how machines exchange keys in preparation to setting up actual encryption (Diffie-Heilman).
So, if the package you’re installing or any application which uses SSL (In this case, this looks like a Python plugin support for SSL) isn’t using <very> recent libraries and code, you’re going to have a problem.
Bottom line is that your error might be a problem with the libraries themselves(You need all libraries to be updated which should include at least your specified package plus openssl plus others your app may use to use your plugin) or could be the application using those libraries. You <might> get specific information if you run a trace development tool to step through your application’s execution.
Lastly, of course an important troubleshooting hint is whether your problem can be replicated by others, is commonly seen by others or if the problem is yours alone.