Re: ssl3_get_record:decryption failed on some machines

2019-11-25 Thread Matt Caswell
ehalf Of > Fernando Gutierrez Mendez > Sent: Monday, November 18, 2019 2:34 PM > To: openssl-users@openssl.org > Subject: Re: ssl3_get_record:decryption failed on some machines > > The writer is my own code but I can also reproduce the problem when server > is nginx and client

RE: ssl3_get_record:decryption failed on some machines

2019-11-25 Thread fergtm
-users On Behalf Of Fernando Gutierrez Mendez Sent: Monday, November 18, 2019 2:34 PM To: openssl-users@openssl.org Subject: Re: ssl3_get_record:decryption failed on some machines The writer is my own code but I can also reproduce the problem when server is nginx and client is my app. In my code I

Re: ssl3_get_record:decryption failed on some machines

2019-11-18 Thread Fernando Gutierrez Mendez
The writer is my own code but I can also reproduce the problem when server is nginx and client is my app. In my code I do not use OpenSSL socket BIOs instead I do read/writes through a BIO pair: pairBase = BIO_new(BIO_s_bio()); pairInt = BIO_new(BIO_s_bio()); [...]

Re: ssl3_get_record:decryption failed on some machines

2019-11-18 Thread Viktor Dukhovni
> On Nov 18, 2019, at 1:44 PM, Fernando Gutierrez Mendez > wrote: > > I use non-blocking IO with a SSL BIO so a call to BIO_read eventually returns > -1, when this happens I call BIO_should_retry to test if this is due an error > or because of the underlying non-blocking transport. Is the

ssl3_get_record:decryption failed on some machines

2019-11-18 Thread Fernando Gutierrez Mendez
Hi, I wrote an application that uses OpenSSL (1.1.1) and for the past couple of weeks I have been unable to solve a very strange issue. I use non-blocking IO with a SSL BIO so a call to BIO_read eventually returns -1, when this happens I call BIO_should_retry to test if this is due an error