> You should fix your tests not to trigger an unexpected EOF. You > probably have code now that ignores the current error, you > shouldn't ignore that error, it's a real error.
Fixing the tests to only consider an ideal world of nicely behaving peers is in my opinion the wrong way to go. Instead I think that it is very useful to have tests which include bad behaved peers since such peers are unfortunately a reality. And it would be good if IO::Socket::SSL would provide a defined and stable behavior in such situations and that the tests check this. As for how this behavior should exactly look like I'm not fully sure yet and I have to figure this out before OpenSSL 3.0.0 gets released. But in any case I rather have the tests fail early (like they also failed with Python and Ruby) when OpenSSL changes behavior in edge cases than have the users code fail somewhere later in production. Regards, Steffen -- Steffen Ullrich Research, Projects and Products steffen_ullr...@genua.de PGP 0x3F84B1A6F7DEAF80 genua GmbH Domagkstrasse 7, 85551 Kirchheim bei Muenchen tel +49 89 991950-0, fax -999, www.genua.de Geschaeftsfuehrer: Matthias Ochs, Marc Tesch Amtsgericht Muenchen HRB 98238 genua ist ein Unternehmen der Bundesdruckerei-Gruppe.