On 2018-04-18 16:14:37 [+0200], Kurt Roeckx wrote:
> I can't see a reason why TLS 1.3 would be different in this regard,
> I expect the same behaviour for all SSL/TLS version. Anyway, it
> could just have been some code refactor that "fixed" it so that it
> generates the error now. Or maybe the old code generated an error
> on SSL_write() instead of the SIGPIPE?
>
> It would at least be good to know how the old version behaved.
As per bisect, openssl commit 30f05b19d3ba ("Create the NewSessionTicket
message in TLSv1.3") is responsible for the SIGPIPE.
But I *think* this is unrelated. The perl testcase triggers reliable. My
C test case I used yestrday triggers only under strace (but I think this
was not the case yesterday). So I *think* this commit changed the
timming and now the SIGPIPE is more likely.
> Kurt
Sebastian
