This has now been applied, thanks for the contribution.
Ticket closed.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4435
Please log in as guest with
Fixed now, thanks for the report.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3826
Please log in as guest with password guest if prompted
--
No problems reported, ticket closed.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4147
Please log in as guest with password guest if prompted
--
On Sun, May 08, 2016 at 12:15:56PM +0100, Alessandro Ghedini wrote:
> I know that I'm probably getting way ahead of myself here, but I thought it
> would be interesting to start looking into adding TLS 1.3 support to OpenSSL
> (for post 1.1.0 of course).
Even after 1.1.0, TLS 1.3 might not be
This is cool.
I think lots of things will be broken for TLS 1.3, but haven't looked at
implementation at all. And "early data" will mean API changes, although I'm
fine if that doesn't happen in the first release :)
Good luck :)
--
openssl-dev mailing list
To unsubscribe:
Hello everyone,
I know that I'm probably getting way ahead of myself here, but I thought it
would be interesting to start looking into adding TLS 1.3 support to OpenSSL
(for post 1.1.0 of course).
Unfortunately I didn't get very far, so I'm hoping someone more experienced
in TLS 1.3 and
Every function that returns an int in crypto/threads_win.c returns 0
immediately if the function called from inside the function fails
except CRYPTO_THREAD_run_once() which returns 1 immediately if the
function called from inside the function succeeds.
InitOnceExecuteOnce returns 0 on failure
