Jakob,
Thank you very much for your help! You have put the finger on the source of the
problem I think.
See my clarifications below based on your remarks:
> Please try the trace again with openssl s_client from each tested OpenSSL
> version, to eliminate any issues in the curl code, such as the
on to aur.archlinux.org:443
== Info: Closing connection 0
Protocol version is at byte offset 4 & 5.
*From:*owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] *On Behalf Of *Le Huang
*Sent:* Thursday, February 28, 2013 8:17 PM
*To:* openssl-users@openssl.org
*Subjec
sl-users@openssl.org
Subject: Re: TLS ClientHello v3.3 not supported by all servers
Olivier,
The command line you provided just worked fine in my box, in which a fresh
openssl-1.0.1e installed.
On Fri, Mar 1, 2013 at 7:31 AM, LANGLOIS Olivier PIS -EXT
mailto:olivier.pis.langl...@transport.alstom.
Olivier,
The command line you provided just worked fine in my box, in which a fresh
openssl-1.0.1e installed.
On Fri, Mar 1, 2013 at 7:31 AM, LANGLOIS Olivier PIS -EXT <
olivier.pis.langl...@transport.alstom.com> wrote:
> They just reset the connection upon the reception of the message.
>
> This
They just reset the connection upon the reception of the message.
This is a new behavior from version 1.0.1-e
1.0.1-d was which sending ClientHello v3.2 are fine.
How to reproduce:
openssl s_client -connect aur.archlinux.org:443
CONFIDENTIALITY : This e-mail an
They just reset the connection upon the reception of the message.
This is a new behavior from version 1.0.1-e 1.0.1-d was which sending
ClientHello v3.2 are fine.
How to reproduce:
openssl s_client -connect aur.archlinux.org:443
CONFIDENTIALITY : This e-mail a
