On 15.05.2013 23:05, Dr. Stephen Henson wrote:
On Wed, May 15, 2013, Johannes Bauer wrote:
Does this mean that communication with TLS1.2 with curves other than the
SEC-curves has actually never worked with OpenSSL (because it couldn't
have worked as this would require the explicit curve
On Thu, May 16, 2013, Johannes Bauer wrote:
On 15.05.2013 23:05, Dr. Stephen Henson wrote:
On Wed, May 15, 2013, Johannes Bauer wrote:
Does this mean that communication with TLS1.2 with curves other than the
SEC-curves has actually never worked with OpenSSL (because it couldn't
have
From: owner-openssl-us...@openssl.org On Behalf Of Johannes Bauer
Sent: Wednesday, 15 May, 2013 11:49
I'm having trouble getting a TLS 1.2 with EC F_p certificates to run.
This is my setup:
Server: openssl 1.0.1e compiled from source, Debian squeeze
Client: openssl 1.0.1c from Gentoo tree
On 15.05.2013 17:48, Johannes Bauer wrote:
Server: openssl 1.0.1e compiled from source, Debian squeeze
Client: openssl 1.0.1c from Gentoo tree
Additional info: Just upgraded the Client to 1.0.1e (Gentoo) and have
the same issue. Something is *seriously* wrong here. That's what the
server says
On 15.05.2013 20:52, Dave Thompson wrote:
I can't easily test at the moment (even assuming your client is OpenSSL),
but I speculate that in SSL3 mode the client doesn't send (Client)Hello
extensions for SupportedCurves and SupportedPointFormats,
Correct.
and in TLS
mode(s?) it does.
On 15.05.2013 21:17, Johannes Bauer wrote:
Only sect/secp are included curiously although my openssl client
does internally also know, for example, about the wap-wsg and X9.62
curves. But those are not included in the Client Hello request.
And there's definitely no unnamed generic type
On Wed, May 15, 2013, Johannes Bauer wrote:
Does this mean that communication with TLS1.2 with curves other than the
SEC-curves has actually never worked with OpenSSL (because it couldn't
have worked as this would require the explicit curve type why doesn't
appear to be implemented as of