cording to OpenSSL 1.1.1 documentation:
For SSL_read() and SSL_peek() the following return values can occur:
<= 0
The read operation was not successful, because either the connection was
closed, an error occurred or action must be taken by the calling process. Call
SSL_get_e
On Thu, Oct 24, 2013 at 03:59:08PM -0400, Dave Thompson wrote:
>0 The shutdown is not yet finished. Call SSL_shutdown() for a
> second
>time, if a bidirectional shutdown shall be performed. The output
> of SSL_get_error(3) may be misleading, as
> From: owner-openssl-users On Behalf Of Dave Mitchell
> Sent: Thursday, October 24, 2013 06:25
> On Sun, Oct 20, 2013 at 09:29:53PM +0100, Dave Mitchell wrote:
> > The man page for SSL_get_error() lists the SSL_* functions it can be
used
> > with, and it doesn&#
On Sun, Oct 20, 2013 at 09:29:53PM +0100, Dave Mitchell wrote:
> The man page for SSL_get_error() lists the SSL_* functions it can be used
> with, and it doesn't mention SSL_shutdown().
>
> On the other hand, the man page for SSL_shutdown() says that for
> non-blocking
The man page for SSL_get_error() lists the SSL_* functions it can be used
with, and it doesn't mention SSL_shutdown().
On the other hand, the man page for SSL_shutdown() says that for
non-blocking I/O, you should call SSL_get_error().
So which is right?
I ask, because in the following
If so what are the conditions ?
> The man page for SSL_write() mentions that I should call
> SSL_get_error() upon failure:
> http://www.openssl.org/docs/ssl/SSL_write.html
>
> Is that all I have to do? Or do I should I inspect the error
> stack too?
IIRC you always need to check and clear the error stack whe
The man page for SSL_write() mentions that I should call
SSL_get_error() upon failure:
http://www.openssl.org/docs/ssl/SSL_write.html
Is that all I have to do? Or do I should I inspect the error stack too?
I guess I don't have any specific question here, just looking for discussion.
-Pa
I'm curious why does SSL_get_error() need to be passed a return code
to function? The call sig being
int SSL_get_error(const SSL *ssl, int ret);
I'm referring to the second argument. I just can't imagine what that
might possibly be for, but I'm extremely, anybody have any i
Hi, All,
How is the relationship between SSL_get_error() and errno? For example, when
SSL_read() return SSL_ERROR_WANT_READ, the errno is EWOULDBLOCK or EAGAIN?
Thanks in advance.
Best regards,
Tom
SSL_get_error return ?
Should SSL_get_error return SSL_ERROR_WANT_READ/SSL_ERROR_WANT_WRITE?
considering that its a fatal error causing handshake
failure? I have checked some of the sites/manuals I could not get any
direct refernce for SSL_get_error return values for such scenario.
Please provide your
Title: ERR_get_error() or SSL_get_error()?
If SSL_accept() returns <= 0, and I want to see what the error is, should I be calling this to get a string description of the error:
int ret = SSL_accept();
if (ret <= 0)
{
char buf[256];
ERR_error_string_n(ERR_get_error(
Hi
For the scenario where the Proxy server is establishing a TLS connection
with a UA and if UA fails to send “Change Cipher Spec, Encrypted Handshake
Message.” resulting in SSL_connect failure. In this case what does
SSL_get_error return ?
Should SSL_get_error return SSL_ERROR_WANT_READ
13 matches
Mail list logo
