Looping in upstream:
On Sun, Mar 22, 2020 at 02:57:54PM +0100, Lucas Nussbaum wrote:
> Version: 1.3.9-8
This is the same version of the serf package that's been in Debian since
2019/12/31, so something else seems to have changed.
> [...]
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > [...]
> > Trailer-Test: f
> > 140691743627136:error:14095126:SSL routines:ssl3_read_n:unexpected eof
> > while reading:../ssl/record/rec_layer_s3.c:302:
> > ..........................F.......................................
> >
> > There was 1 failure:
> > 1) test_ssltunnel_basic_auth_server_has_keepalive_off:
> > test/test_context.c:2138: expected <0> but was <120199>
Running a bisect against what's changed in the archive, shows that the
test started failing when OpenSSL's version changed from 1.1.1d-2 to
1.1.1e-1.
Looking at OpenSSL's changelog, it seems this was a change on their end
that's affecting serf.
Changes between 1.1.1d and 1.1.1e [17 Mar 2020]
*) Properly detect EOF while reading in libssl. Previously if we hit an EOF
while reading in libssl then we would report an error back to the
application (SSL_ERROR_SYSCALL) but errno would be 0. We now add
an error to the stack (which means we instead return SSL_ERROR_SSL) and
therefore give a hint as to what went wrong.
[Matt Caswell]
I guess serf needs to adapt to this change in behavior.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
