M2Crypto 0.20.1 won't build on Red Hat Linux

John Nagle nagle at animats.com
Fri Oct 2 20:06:10 CEST 2009


Heikki Toivonen wrote:
> John Nagle wrote:
>> The right question is "uname --hardware-platform".  That returns "i386" if
>> running on something emulating a 386, even it it's 64-bit capable.
> 
> Thanks, I'll make a note that I'll need to clarify that part.
> 
>> With that change, the build runs to completion and and the regression tests
>> mostly run.  Test failure occurred at:
>>
>> ======================================================================
>> FAIL: test_cipher_ok (tests.test_ssl.MiscSSLClientTestCase)
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>>   File
>> "/var/www/vhosts/sitetruth.com/private/downloads/M2Crypto/M2Crypto-0.20.1/tests/test_ssl.py",
>> line 485, in test_cipher_ok
>>     assert s.get_cipher().name() == 'AES128-SHA', s.get_cipher().name()
>> AssertionError: AES256-SHA
>>
>> ----------------------------------------------------------------------
>> Ran 226 tests in 91.672s
>>
>> Is 'AES128-SHA' a cypher that Fedora Core doesn't support, or what?
> 
> That seems strange. OpenSSL does allow fine tuning what ciphers to build
> and operate with, but this is the first I hear AES128-SHA might not be
> turned on anymore. And even stranger still is that the test is
> explicitly asking for 128 yet it is getting 256 back. Could you rerun
> the test again just to make sure you can repeat it, and if so, let me
> know the fedora core, openssl, swig and python versions?

   Ran it again.  Same error.

python setup.py test
...
test_blocking0 (tests.test_ssl.MiscSSLClientTestCase) ... ok
test_blocking1 (tests.test_ssl.MiscSSLClientTestCase) ... ok
test_cipher_mismatch (tests.test_ssl.MiscSSLClientTestCase) ... ok
test_cipher_ok (tests.test_ssl.MiscSSLClientTestCase) ... FAIL
test_info_callback (tests.test_ssl.MiscSSLClientTestCase) ... LOOP: SSL connect: 
before/connect initialization
LOOP: SSL connect: SSLv2/v3 write client hello A
...
test_26_compat (tests.test_ssl.FtpslibTestCase) ... ok

======================================================================
FAIL: test_cipher_ok (tests.test_ssl.MiscSSLClientTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
   File 
"/var/www/vhosts/sitetruth.com/private/downloads/M2Crypto/M2Crypto-0.20.1/tests/test_ssl.py", 
line 485, in test_cipher_ok
     assert s.get_cipher().name() == 'AES128-SHA', s.get_cipher().name()
AssertionError: AES256-SHA

----------------------------------------------------------------------
Ran 226 tests in 166.875s

FAILED (failures=1)

System info:

-bash-3.1$ uname -r -v
2.6.18-1.2239.fc5smp #1 SMP Fri Nov 10 13:22:44 EST 2006

-bash-3.1$ python --version
Python 2.5

-bash-3.1$ swig -version

SWIG Version 1.3.31

Compiled with i386-redhat-linux-g++ [i386-redhat-linux-gnu]
Please see http://www.swig.org for reporting bugs and further information

-bash-3.1$ openssl
OpenSSL> version
OpenSSL 0.9.8a 11 Oct 2005
OpenSSL>

So, per "http://chandlerproject.org/bin/view/Projects/MeTooCrypto":

Required Python version: 2.4 or newer.  Using Python 2.5.  REQUIREMENT MET.
Required SWIG version: 1.3.30 or newer.  Using SWIG 1.3.31  REQUIREMENT MET.
Required OpenSSL version: 0.9.8 or newer: Using OpenSSL 0.9.8a. REQUIREMENT MET.

				John Nagle








More information about the Python-list mailing list