On Fri, Jan 31, 2014 at 10:47 AM, Tim Roberts t...@probo.com wrote:
Bharath Ramesh wrote:
We use numerous third party libraries, one being PyOpenSSL We have
already rebuilt it with a newer version of OpenSSL. We continue to
have the same issue. We have some part of the code that make secure
Bharath Ramesh wrote:
I am not sure if I am correct in describing what is possibly
happening. I have OpenSSL statically compiled with Python v0.9.8. I
have another third party library that uses another version of OpenSSL
1.0.1, linked dynamically. My application is dynamically linked with
the
On Mon, Feb 3, 2014 at 11:44 AM, Tim Roberts t...@probo.com wrote:
Bharath Ramesh wrote:
I am not sure if I am correct in describing what is possibly
happening. I have OpenSSL statically compiled with Python v0.9.8. I
have another third party library that uses another version of OpenSSL
Bharath Ramesh wrote:
On Mon, Feb 3, 2014 at 11:44 AM, Tim Roberts t...@probo.com wrote:
The Python ssl module will always use its statically linked library. It
doesn't care which dynamic libraries are loaded -- the external
references it needs were already satisfied at link time.
Would it
