Actually my intention was to test if the problem can be reproduced with
*same binary*. That's why I suggested that you, Kurt, compile one and
hand it to user. Other way around would also work, i.e. user hands over
the binary. This is because I don't exclude possibility for compiler bug...
As soon as user can confirm that
http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=5702e965d759dde8a098d8108660721ba2b93a7d
does the trick, it goes to stable branches.
Yes, the user confirmed that this fixed the issue.
Populated. For reference. Original report effectively said
The commit has a typo, the second line should read *STDOUT=*OUT;.
The fix works, thanks!
Yes, it was fixed few minutes after. Dismissing the case.
__
OpenSSL Project http://www.openssl.org
Hello!
I'm using OpenSSL 1.0.1c on a 64bit Gentoo Linux, and there is a server
which hangs after sending the first packet. The server does not support
TLS 1.1 or 1.2, only 1.0. Opera with TLS 1.2 enabled, and Internet
Explorer with TLS 1.2 enabled does not hang.
Test code:
$ echo -en 'GET
On Mon Mar 18 20:37:23 2013, zhala...@loginet.hu wrote:
Hello!
I'm using OpenSSL 1.0.1c on a 64bit Gentoo Linux, and there is a server
which hangs after sending the first packet. The server does not support
TLS 1.1 or 1.2, only 1.0. Opera with TLS 1.2 enabled, and Internet
Explorer with TLS
On Mon, Mar 18, 2013 at 5:42 AM, Erwann Abalea
erwann.aba...@keynectis.com wrote:
That CSR is clearly invalid, because one of its objects isn't properly DER
encoded.
This is precisely my point. All of the OpenSSL calls I make succeed
including PEM_write_X509_REQ. Either,
- the call to
On 03/17/2013 04:15 PM, David Woodhouse wrote:
On Fri, 2013-03-15 at 17:17 +0100, Lutz Jaenicke wrote:
The new server currently hosting the www, git, rt, ftp, and cvs
services is going to be moved within the installation of our hoster.
As a consequence, the system will be assigned a new IP
Hello openssl-dev. I've run into an issue using OpenSSL to verify a
certificate chain from an Infineon TPM endorsement key. This is not an
OpenSSL bug, but rather an issue handling certificates deployed in the
wild.
I believe Infineon may have published intermediate certificates with
an invalid
