SSL_CTX_set_options not working for SSL_OP_NO_TLSv1_1

2012-08-31 Thread Jahn, Gerhard
Hello, I'm usinng OpenSSL 1.0.1c in my Server application. This application can be configured to disallow accepting certain SSL/TLS protocols. If only TLS1.2 shall be allowed, the application calls meth=(SSL_METHOD*) SSLv23_server_method(); OpenSSLctx=SSL_CTX_new(meth); .

RE: SSL_CTX_set_options not working for SSL_OP_NO_TLSv1_1

2012-09-03 Thread Jahn, Gerhard
that context. Erik Erik Tkal Juniper OAC/UAC/Pulse Development From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Jahn, Gerhard Sent: Friday, August 31, 2012 5:33 AM To: 'openssl-users@openssl.org' Subject: SSL_CTX_set_options

RE: SSL_CTX_set_options not working for SSL_OP_NO_TLSv1_1

2012-09-03 Thread Jahn, Gerhard
Of Jahn, Gerhard Sent: Friday, August 31, 2012 5:33 AM To: 'openssl-users@openssl.org' Subject: SSL_CTX_set_options not working for SSL_OP_NO_TLSv1_1 Hello, I'm usinng OpenSSL 1.0.1c in my Server application. This application can be configured to disallow accepting certain SSL/TLS protocols

RE: C API to determine OpenSSL version?

2012-09-05 Thread Jahn, Gerhard
Hi Charles, I'm using SSLeay_version(SSLEAY_VERSION) in my app. This returns a human readable string containing the OpsnSSL version like: OpenSSL 1.0.1c 10 May 2012 Mit freundlichen Gr??en/Regards - Gerhard Jahn Tel.: +49 (89) 636-44657 Tel.: +49 (211)

Re: [openssl-users] SSL_connect returns SSL_ERROR_SYSCALL and errno == EWOULDBLOCK

2018-09-10 Thread Jahn, Gerhard
penssl-users@openssl.org Subject: Re: [openssl-users] SSL_connect returns SSL_ERROR_SYSCALL and errno == EWOULDBLOCK On 07/09/18 09:16, Jahn, Gerhard wrote: > Hi, > > We are using OpenSSl 1.0.2n in our server running on LINUX. > We call SSL_connect() on async socket (after TCP connect c

[openssl-users] SSL_connect returns SSL_ERROR_SYSCALL and errno == EWOULDBLOCK

2018-09-08 Thread Jahn, Gerhard
Hi, We are using OpenSSl 1.0.2n in our server running on LINUX. We call SSL_connect() on async socket (after TCP connect completion) to establish a secure connection. According to DOC SSL_get_error(() has to be called if SSL_connect() returns <=0 We do not understand what to do if

RE: SSL_get_error() crash (shortened)

2019-09-12 Thread Jahn, Gerhard
Hello, We're using OpenSSl 1.1.1b on WIN64 and are facing a (rare but strange) core-dump when doing the following: After successful TLS1.3 handshake we're calling SSL_read() to get the first 2 Bytes of PDU data from the new connection (ASN.1 TAG + length). SSL_read() returns 0 According to