Openssl compatibility with AIX 5.3

2012-03-12 Thread Vishal Pathak
Hi Team, I am facing issue while I use Crypt::SSLeay module in one of my perl scripts. I just need to know if openssl 9.8t is compatible with AIX 5.3 V12 or not. If not then which relase of openssl I should use. Quick response would be highly appreciable. Thanks, Vishal Pathak.

OpenSSL security advisory

2012-03-12 Thread OpenSSL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OpenSSL Security Advisory [12 Mar 2012] === CMS and S/MIME Bleichenbacher attack (CVE-2012-0884) A weakness in the OpenSSL CMS and PKCS #7 code can be exploited

Re: OpenSSL security advisory

2012-03-12 Thread carlyoung
On Mon 12/03/12 4:02 PM , open...@master.openssl.org (OpenSSL) sent: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OpenSSL Security Advisory [12 Mar 2012] FTAO Dr Steve Henson, Not that it's important, but the FAQ in 0.9.8u archive says: * Which is the current version of OpenSSL? The

Re: Tutorials on OpenSSL integration with nCipher HSM (nShield) ?

2012-03-12 Thread Sunjeet Singh
If the MS-CAPI Engine can generate keys, you might be able to use it through the nCipher CSP to generate hardware protected Signing and Exchange keypairs for your CAPI container. I just accomplished this by making use of the nCipher CSP and their command line utility keytst to generate a

RE: Please Clarify : Unable to verify leaf signature (21)

2012-03-12 Thread Dave Thompson
From: owner-openssl-us...@openssl.org On Behalf Of Mr.Rout Sent: Saturday, 10 March, 2012 02:33 To: openssl-users@openssl.org Subject: Re: Please Clarify : Unable to verify leaf signature (21) Thanks Dave. I request you please give more information regarding this error. What exactly

SSL_read / SSL_ERROR_WANT_READ / ENOTCONN infinite loop ...

2012-03-12 Thread Steven Parkes
This is on iOS, which can do some fairly aggressive things when you background an app, including (apparently) locally tearing down a socket connection. What I'm seeing is SSL_read returning SSL_ERROR_WANT_READ forever. Tracking this down the stack, it's coming from BIO_sock_non_fatal_error