There are no plans, at this point, to change the names used in logging.
If you think it's worthwhile, please open a *github issue* for this.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=3728
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To
On Thu 2015-03-05 08:58:10 -0800, Matt Caswell via RT wrote:
On Thu Mar 05 17:42:49 2015, richard.c.pater...@sas.com wrote:
Apologies if this is the incorrect forum for this question.
We’re
seeing error messages like SSL3_READ_BYTES and
SSL3_GET_SERVER_CERTIFICATE for some reason;
-
On Thu 2015-03-05 08:58:10 -0800, Matt Caswell via RT wrote:
On Thu Mar 05 17:42:49 2015, richard.c.pater...@sas.com wrote:
Apologies if this is the incorrect forum for this question.
We’re
seeing error messages like SSL3_READ_BYTES and
SSL3_GET_SERVER_CERTIFICATE for some reason;
-
On Sat, Mar 07, 2015 at 09:56:36AM -0800, Daniel Kahn Gillmor wrote:
No. These are just the names of internal functions. Originally written when
it
was just a choice of ssl2 or ssl3 they were subsequently reused for TLS -
but
the names have remained the same.
Is there a plan to
Apologies if this is the incorrect forum for this question.
We’re seeing error messages like SSL3_READ_BYTES and
SSL3_GET_SERVER_CERTIFICATE for some reason;
- SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
- SSL£_GET_BYTES:sslv3 alert handshake failure
However, we
On Thu Mar 05 17:42:49 2015, richard.c.pater...@sas.com wrote:
Apologies if this is the incorrect forum for this question.
We’re
seeing error messages like SSL3_READ_BYTES and
SSL3_GET_SERVER_CERTIFICATE for some reason;
-
SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
-
