Bug#954371: [Pkg-openssl-devel] Bug#954371: libio-socket-ssl-perl: FTBFS since openssl 1.1.1e

2020-03-31 Thread Steffen Ullrich
roduction. 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

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

2019-05-13 Thread Steffen Ullrich
> Ah I see, thanks for the clarification. I thought you meant it could > yield a deadlock. Aren't temporary failures also possible on plain > sockets (though of course the extra SSL layer make it strictly more > likely to happen)? IIRC if the checksum of the incoming packet > mismatches, which

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

2019-05-13 Thread Steffen Ullrich
On Mon, May 13, 2019 at 03:18:14PM +0200, Guilhem Moulin wrote: > On Mon, 13 May 2019 at 06:31:26 +0200, Steffen Ullrich wrote: > > Applications which relied on blocking I/O in connection with select could > > also hang before, > > Uh, what? “Before” meaning with ≤TLS

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

2019-05-12 Thread Steffen Ullrich
On Mon, May 13, 2019 at 01:02:45AM +0200, Guilhem Moulin wrote: > Thanks for your analysis, Steffen. Dropping the Debian-specific patch > is definitely the way to go for libwww/LWP. However I still believe > IO::Socket::SSL should provide a way to clear SSL_MODE_AUTO_RETRY in > order to fix

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

2019-05-11 Thread Steffen Ullrich
(from 2003) instead of introducing yet another patch. Regards, Steffen On Sun, May 12, 2019 at 01:11:45AM +0200, gregor herrmann wrote: > On Sat, 11 May 2019 21:56:01 +0200, Steffen Ullrich wrote: > > > I think the issue is a bit different than what was analyzed so far. > […

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

2019-05-11 Thread Steffen Ullrich
I think the issue is a bit different than what was analyzed so far. As far as I can see it has nothing to do with SSL_MODE_AUTO_RETRY but instead is caused by expectations on the behavior of select which are wrong with TLS 1.3. I've added some more debugging to IO::Socket::SSL and what I saw

Bug#914034: Bug#911938: libhttp-daemon-ssl-perl FTBFS: tests fail: Connection refused

2019-04-08 Thread Steffen Ullrich
lems you see. Regards, Steffen Ullrich, Maintainer IO::Socket::SSL.

Bug#848346: should be solved with 2.040

2016-12-17 Thread Steffen Ullrich
Thanks for the analysis that the problem is caused by a change in the SSLEAY_DIR/OPENSSL_DIR constant with OpenSSL 1.1. I've adapted IO::Socket::SSL in 2.040 (just released) to try both constants so the problem should hopefully be solved by simply upgrading to 2.040. Apart from that the

Bug#764868: IO::Socket::SSL - external tests in test suite can be disabled but are enabled by default

2014-10-12 Thread Steffen Ullrich
Thanks! I think the least intrusive thing for now would be to change the default of the Makefile.PL prompt if NO_NETWORK_TESTING is set. Would that be OK with you? This check will be included in the next version. See

Bug#764868: IO::Socket::SSL - external tests in test suite can be disabled but are enabled by default

2014-10-11 Thread Steffen Ullrich
Hi, I'm the maintainer of IO::Socket::SSL and I've just found your serious problem report about IO::Socket::SSL doing network connections to external sites during testing. IO::Socket::SSL will ask during the build, if the tests should be run and you can deny running external tests. But, the

Bug#746579: Fix can be found here

2014-05-04 Thread Steffen Ullrich
On Sun, May 04, 2014 at 08:42:05AM +0200, Salvatore Bonaccorso car...@debian.org wrote: Hi Steffen, On Sat, May 03, 2014 at 11:28:30PM +0200, Steffen Ullrich wrote: https://github.com/libwww-perl/lwp-protocol-https/pull/14 Thanks for the patch, I have commited it to the git repo[1