IO::Socket::SSL & non-ActiveState Perl for Windows?

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

We build our own Perl distribution for Windows 2000 & above, since it's redistributed with our product, and it has to be placed in the filesystem in ways that ASP doesn't much care for.

I'd like to use it for some LDAP/SSL components of that product, so I need IO::Socket::SSL, Net::SSLeay, etc.

I've successfully compiled those packages, but they hang in their tests, particularly where they try to fork servers. Yet the version of ActiveState I've got on my desk works just fine, at least for HTTPS using LWP. Any idea where I should be looking for a clue? Or should I write off the tests and move on to trying a client?

Comment on IO::Socket::SSL & non-ActiveState Perl for Windows?

Replies are listed 'Best First'.
Re: IO::Socket::SSL & non-ActiveState Perl for Windows? by Anonymous Monk on Mar 24, 2004 at 05:06 UTC
I've successfully compiled those packages, but they hang in their tests, particularly where they try to fork servers... Any idea where I should be looking for a clue? Or should I write off the tests and move on to trying a client? Which distribution and which tests hang precisely (be specific)? Did you check cpan-testers/rt? Did you try redesigning the tests (remove fork from the picture)? Did you contact the authors? I highly suggest not moving on because these kinds of things have a habit of coming back to bite you in the rear, and it's best to take care of them once and for all (you won't be the last person to encounter this).	[reply]
Re: Re: IO::Socket::SSL & non-ActiveState Perl for Windows? by Anonymous Monk on Mar 25, 2004 at 06:08 UTC
Thanks for the pointers. I'll check with cpan-testers/rt. I think removing the fork is somewhat problematic, since you need both a client and a server for these tests, but perhaps a full "perl ... &" with a later kill will work. I'll describe the failed tests from SSLeay here, since one can hope that those cause the failed tests in IO::Socket::SSL. Compilation environment: Visual C++ 7.1 (.NET 2003) The Perl Core is 5.8.3 stable.tar.gz Net_SSLeay.pm-1.25 IO-Socket-SSL-0.95 OpenSSL-0.9.7c Net_SSLeay.pm crashes in test 5 and maybe 6; it's hard to tell because the minidumper dialog comes up twice (no, I haven't tried splitting the specific tests out). The minidumper dialog comes up with no information, since Perl's compiled using the defaults (optimized, etc). The transcript is (about 10 minutes into the test)... ok 1 Testing pointer to int casting... cc: cl Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for +80x86 Copyright (C) Microsoft Corporation 1984-2002. All rights reserved. ptrcasttst.c Microsoft (R) Incremental Linker Version 7.10.3077 Copyright (C) Microsoft Corporation. All rights reserved. /out:ptrcasttst.exe /out:ptrcasttst.exe ptrcasttst.obj ok ./ptrcasttst: 'void ' len: 4, 'unsigned long int' len: 4. ptrcasttst: ok (00320F60 == 00320F60). ok ok ok 2 ok 3 ok 4 Spawning a TCP test server on port 1211, pid=-3920... ** not ok 5tcp Spawning a SSL test server on port 1212, pid=-2720... ok 5 ok 6 ok 7 ok 8 ok 9 Sending 1 MB over localhost, may take a while (and some VM)... ...took 1 secs (1024 KB/s) ok 10 3512: ssl read failed at examples/cli-cert.pl line 53. [download]	[reply] [d/l]