We have some interop issue between TLS 1.0 and TLS 1.1. Our application is
based on OpenSSL 0.9.7 version (Linux - Operation system). This is Radvision
SIP stack and oSIP stack.
I don't quite understand. Does OpenSSL act as server or client? You must
be referring to server...
It doesn't
we are using openssl in an environment with a Windows 2003 PKI/CA.
OpenSSL together with OpenLDAP shall be used to provide Single Sign On.
This is working as long as the servers public key on the Windows AD
server is not getting larger than 1024 bit.
I have tested the following commands
[EMAIL PROTECTED] via RT wrote:
Hi,
I am having a bit of a trouble compiling the openSSL release 0.9.8e
under WinXP SP2.
The version of minGW's the gcc compiler I am using is 3.4.5-20060117-1
and the minGW32-make is 3.80.0-1.
For some reason the build tools use malformed file names
0.9.7 is no longer [actively] supported. Mac OS support is improved in
0.9.8 stable and development versions and we advice to use them instead. A.
__
OpenSSL Project http://www.openssl.org
This was fixed at some point. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
On Tue, 18 Sep 2007 15:44:46 +0200 (CEST)
Ben Laurie via RT [EMAIL PROTECTED] wrote:
According to our records, your request has been resolved. If you have
any further questions or concerns, please respond to this message.
I don't agree with this, as steve stated in a previous email:
Instead
On Tue, 18 Sep 2007 15:44:46 +0200 (CEST)
Ben Laurie via RT [EMAIL PROTECTED] wrote:
According to our records, your request has been resolved. If you have
any further questions or concerns, please respond to this message.
I don't agree with this, as steve stated in a previous email:
Instead
We have been building OpenSSL on PPC64 and S390X platforms with Linux
and have found some type punning errors in both the 0.9.7 tree and the
0.9.8 tree. The self-test test_x509 fails due to this error. This error
only seems to appear on big endien 64 bit machines, whether compiling
for 32 or
On Tue, Sep 18, 2007, Pierre-Yves Ritschard via RT wrote:
On Tue, 18 Sep 2007 15:44:46 +0200 (CEST)
Ben Laurie via RT [EMAIL PROTECTED] wrote:
According to our records, your request has been resolved. If you have
any further questions or concerns, please respond to this message.
I
This transaction appears to have no content
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Hi Steve, thanks for replying !
Well other than the new error codes you are largely making use of
documented functions in OpenSSL so that the whole functionality could
be implemented (with few changes) outside the ssl library at an
application level.
Alright. I could indeed. But this is
Hi,
I've created very small patch that uses default CApath ($OPENSSLDIR/certs/), it
allows apps using OpenSSL and not allowing to specify CApath to function
correctly. Most Linux distributions install certificates (for example root
certificate for CACert) there.
Before patch:
$ wget
Andy -
These fixes look great and solve the underlying problem we encountered with
x_name.c and assumed byte-ordering.
We will re-test with these fixes and get back to you, but for now please
consider this case closed (and fixed).
Thanks,
Mike
Michael Kobar [EMAIL
13 matches
Mail list logo
