Yes, I realize that this is an error in API use on our part, and we will adjust
our logic.
I just filed this issue because what was an error return in 1.0.1 has become a
seg fault in 1.0.2, and it looks like the segfault could be avoided with minor
effort, which I noted in the bug description.
On Wednesday, June 15, 2016 8:43 PM, Rich Salz via RT <r...@openssl.org>
wrote:
Please look at the WARNINGS section in SSL_write.pod; you must call it with the
exact same arguments (it has been there sincethe turn of the century :).
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4574
Please log in as guest with password guest if prompted
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4574
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
