On Mon Nov 03 18:48:34 2014, BOOK wrote:
Show quoted text> On Mon Nov 03 17:06:51 2014, CHORNY wrote:
> > 1..5
> > # Random seed 1209204735
> > # ports: 1142 1143
> > 2014-11-03 23:44:24 SSL connect accept failed because of handshake
> > problems error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert
> > unknown ca at C:\strawberry182\cpan\build\Net-Proxy-0.13-
> > lGr41T\blib\lib/Net/Proxy/Connector/ssl.pm line 73.
> >
> > ok 1 # skip Couldn't start the client: Bad file descriptor
> > ok 2 # skip Couldn't start the client: Bad file descriptor
> > ok 3 # skip Couldn't start the client: Bad file descriptor
> > ok 4 # skip Couldn't start the client: Bad file descriptor
> > ok 5 # skip Couldn't start the client: Bad file descriptor
> > (hangs)
> >
> > possibly hangs only on 5.18.x and not earlier.
>
> Which version of the SSL libraries (Net::SSLeay and IO::Socket::SSL)
> are installed?
Net::SSLeay 1.55, IO::Socket::SSL 1.967
Show quoted text> The error (unknown CA) seems legitimate, given the
> tests are done with a self-signed certificate. I guess I can probably
> get rid of the error with the appropriate environment variable.
error is "alert unknown" and SSL_verify_mode does not prevent this error
Show quoted text>
> However the hanging after failure is probably specific to Windows.
> I'm wondering if closing all the sockets wouldn't help.
>
> Could you try the attached patch and tell me what happens?
Same hanging.
--
Alexandr Ciornii,
http://chorny.net