> So the test expects no error. Since the commit mention there is an > error where earlier there was none. From the Changes file: > > | *) 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. > > OpenSSL 1.1.1d with the commit question leads to this behaviour.
isnt this a regression in openssl then? why there's no RC bug filed against openssl and you filed this bug against a downstream package? i'm still not clear what you expect us to do with regards to m2crypto: should we skip the failing test? -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
