Bug #111556 for IO-Socket-SSL: t/startssl-failed.t hangs with openssl-1.0.2f

Fri Jan 29 18:32:21 2016 GAAS [...] cpan.org - Ticket created

Subject:

t/startssl-failed.t hangs with openssl-1.0.2f

The t/startssl-failed.t test just hangs when using a Net-SSLeay that links with openssl-1.0.2f. With the 1.0.2e release this wasn't an issue. I see this on multiple platforms; linux, osx, windows.

When I run the test directly I see this output and I get accumulate a hanging background process:

gisle@myrull:~/IO-Socket-SSL-2.022$ perl -Mblib t/startssl-failed.t

1..9

ok #Server Initialization

ok #client tcp connect

ok #tcp accept

ok #send non-ssl data

Alarm clock: 14

gisle@myrull:~/IO-Socket-SSL-2.022$ ps -u gisle | grep startssl

501 30350 ttys007 0:13.56 perl -Mblib t/startssl-failed.t

501 30359 ttys007 0:00.00 grep startssl

Sat Jan 30 06:14:36 2016 Steffen_Ullrich [...] genua.de - Correspondence added

Am Fr 29. Jan 2016, 18:32:21, GAAS schrieb: Show quoted text

> The t/startssl-failed.t test just hangs when using a Net-SSLeay that > links with

Thanks for reporting the issue. It looks like that 1.0.2f changed the behavior of SSL_shutdown for the case that the SSL connection is not yet fully open. This resulted in an endless loop when trying to close down the connection properly. Fixed in the just released version 2.023.

Sat Jan 30 06:14:37 2016 The RT System itself - Status changed from 'new' to 'open'

Sat Jan 30 06:14:40 2016 Steffen_Ullrich [...] genua.de - Status changed from 'open' to 'resolved'

Sat Jan 30 06:20:43 2016 SREZIC [...] cpan.org - Correspondence added

On 2016-01-29 18:32:21, GAAS wrote: Show quoted text

> The t/startssl-failed.t test just hangs when using a Net-SSLeay that > links with > openssl-1.0.2f. With the 1.0.2e release this wasn't an issue. I see > this on > multiple platforms; linux, osx, windows. > > When I run the test directly I see this output and I get accumulate a > hanging > background process: > > gisle@myrull:~/IO-Socket-SSL-2.022$ perl -Mblib t/startssl-failed.t > 1..9 ok > #Server Initialization ok #client tcp connect ok #tcp accept ok #send > non-ssl > data Alarm clock: 14 gisle@myrull:~/IO-Socket-SSL-2.022$ ps -u gisle | > grep > startssl 501 30350 ttys007 0:13.56 perl -Mblib t/startssl-failed.t 501 > 30359 > ttys007 0:00.00 grep startssl

I cannot reproduce the problem on a Debian/sid system (openssl 1.0.2f-2, with self-compiled perl 5.20.3 and system perl 5.22.1).