Hi Everyone,
I'm currently using the networking library libneon (version 31.2) which
internally uses openSSL 1.1.1d
The issue is that a hang occurs at random in SSL_peek_ex() API multiple
times in a day. 'strace ' shows the SSL_peek_ex() API is stuck in an
unfinished read.
Could anyone give me
(Top posting to match what Mr. André does):
TCP without keepalive will time out the connection a few minutes after
sending any data that doesn't get a response.
TCP without keepalive with no outstanding send (so only a blocking
recv) and nothing outstanding at the other end will probably hang
Thanks, please check out https://github.com/openssl/openssl/issues/13424
Regards,
Rui Zang
16.11.2020, 19:45, "Matt Caswell" :
> On 16/11/2020 07:56, rui zang wrote:
>> Resend in plain text.
>> ==
>>
>> Greetings,
>>
>> I am trying openssl+ktls on ubuntu
I'm writing a daemon that talks to a server using HTTP/2 over TLS 1.2+ and
leveraging OpenSSL 1.1.1h to provide the TLS support.
At the moment I think that I have the whole TLS part figured, and I could
probably have the project running by now if I used SSL_set_fd to assign a
connected socket
On 16/11/2020 07:56, rui zang wrote:
> Resend in plain text.
> ==
>
> Greetings,
>
> I am trying openssl+ktls on ubuntu 20.04.
> I have tried openssl-3.0.0-alpha8 from
> https://www.openssl.org/source/openssl-3.0.0-alpha8.tar.gz
> and also the current
On 14/11/2020 11:00, Rahul Godbole wrote:
> Is OpenSSL function RAND_bytes () thread safe?
Short answer: Yes
Longer answer: Yes assuming that:
- you are using >= OpenSSL 1.1.0
or
- you are using OpenSSL 1.0.2 or below and you have set up the locking
callbacks
AND
- You have not compiled
On 13/11/2020 19:10, Narayana, Sunil Kumar wrote:
> Hi ,
>
> We are porting our Application from openssl 1.0.1 to
> openssl 3.0. in related to this activity we require to access the
> variable ‘*ex_kusage*’ pointed by *X509*
>
> But there are no set utilities available to