Heikki Toivonen wrote:
> John Nagle wrote:
>
>>OpenSSL version: "OpenSSL 0.9.7a Feb 19 2003"
>
>
> Hmm, I've never actually used that old OpenSSL myself, just assumed from
> the original author's notes that anything from 0.9.7 onward worked.
> Guess not. I am thinking of changing the require
John Nagle wrote:
> OpenSSL version: "OpenSSL 0.9.7a Feb 19 2003"
Hmm, I've never actually used that old OpenSSL myself, just assumed from
the original author's notes that anything from 0.9.7 onward worked.
Guess not. I am thinking of changing the requirements to state which one
works... I thi
Heikki Toivonen wrote:
> John Nagle wrote:
>
>>Actually, at the moment I'm having an M2Crypto problem related
>>to a SWIG/OpenSSL conflict. Older versions of OpenSSL have an
>>include file that needs __i386__ defined, which is something GCC
>>does based on what platform you're on. SWIG uses
John Nagle wrote:
> Actually, at the moment I'm having an M2Crypto problem related
> to a SWIG/OpenSSL conflict. Older versions of OpenSSL have an
> include file that needs __i386__ defined, which is something GCC
> does based on what platform you're on. SWIG uses CPP, but
> doesn't set the p
John Nagle wrote:
> I've been running M2Crypto successfully using Python 2.4 on Windows 2000,
> and now I'm trying to get it to work on Python 2.3.4 on Linux.
>
> Attempting to initialize a context results in
>
> Traceback (most recent call last):
[...]
> map()[long(self.ctx)] = self
> Va
Gabriel Genellina wrote:
> At Thursday 18/1/2007 04:41, John Nagle wrote:
> On a previous version of M2Crypto that line said: map()[self.ctx] =
> self, and that failed too ("unhashable object", I think).
> I changed the class _ctxmap (the map() above returns an instance of it)
> to use str(key)
At Thursday 18/1/2007 04:41, John Nagle wrote:
I've been running M2Crypto successfully using Python 2.4 on Windows 2000,
and now I'm trying to get it to work on Python 2.3.4 on Linux.
Attempting to initialize a context results in
Traceback (most recent call last):
File "/www/htdocs/si
Upgraded to Python 2.5 on the Linux system, rebuild M2Crypto,
and it stil fails, but the last line of the error message changed to:
ValueError: invalid literal for long() with base 10: '_40f91a08_p_SSL_CTX'
Others have encountered this problem, from a Google search.
Is "long" suppose
I've been running M2Crypto successfully using Python 2.4 on Windows 2000,
and now I'm trying to get it to work on Python 2.3.4 on Linux.
Attempting to initialize a context results in
Traceback (most recent call last):
File "/www/htdocs/sitetruth.com/cgi/ratingdetails.cgi", line 46, in ?
Heikki Toivonen wrote:
> John Nagle wrote:
>
>> A list of small problems and bugs in the current M2Crypto:
>>I need to look at SSL certificates in some detail, so this
>>is all about the access functions for certificates.
>
>
> Thanks, got the reports, will check them out.
>
>
>>3. /M2Cry
John Nagle wrote:
> A list of small problems and bugs in the current M2Crypto:
> I need to look at SSL certificates in some detail, so this
> is all about the access functions for certificates.
Thanks, got the reports, will check them out.
> 3. /M2Crypto/SSL/Connection.py:147:
> Depreca
A list of small problems and bugs in the current M2Crypto:
I need to look at SSL certificates in some detail, so this
is all about the access functions for certificates.
Bugs:
1. Off by one error at "X509.get_ext_count()". Reports
eight extensions on a certificate that only ha
12 matches
Mail list logo
