Hi,
On 31/03/20 19:42, Viktor Dukhovni wrote:
On Tue, Mar 31, 2020 at 04:51:32PM +0200, Christoph Pleger wrote:
I have here a self-written server program and the corresponding
self-written client program. These run well together with libssl 1.1.0l,
but with libssl 1.1.1d, the same programs
On Tue, Mar 31, 2020 at 04:51:32PM +0200, Christoph Pleger wrote:
> > > I have here a self-written server program and the corresponding
> > > self-written client program. These run well together with libssl 1.1.0l,
> > > but with libssl 1.1.1d, the same programs give errors SSL_ERROR_SYSCALL
> >
Hello,
> > I have here a self-written server program and the corresponding
> > self-written client program. These run well together with libssl 1.1.0l,
> > but with libssl 1.1.1d, the same programs give errors SSL_ERROR_SYSCALL
> > in SSL_read(), no matter if I recompile the programs and then run
On 31/03/2020 15:21, Salz, Rich via openssl-users wrote:
> Isn't this the SSL EOF thing?
No. In older OpenSSL's SSL_read() would return SSL_ERROR_SYSCALL on EOF
with an errno of 0. This was "fixed" in 1.1.1e to return SSL_ERROR_SSL
with an entry on the error stack. And unfixed in 1.1.1f to
Isn't this the SSL EOF thing?
On Tue, Mar 31, 2020 at 11:27:27AM +0200, Christoph Pleger wrote:
> I have here a self-written server program and the corresponding self-written
> client program. These run well together with libssl 1.1.0l, but with libssl
> 1.1.1d, the same programs give errors SSL_ERROR_SYSCALL in SSL_read(),
