Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Did you try IO::Socket::SSL? It's an alternative to Crypt::SSLeay. It does depend on Net::SSLeay however. Also, when I last used it, timeouts didn't work properly. But apart from that it works fine.

    -Dom

    • We didn't try it, but it looks like it might run into silimar compilation problems. We can't really try it out now either, because the problem only occurs on the production machines (Which is really weird because the test machines are 99.999% identical).

      Does the module provide an Interface to LWP? If not it might be a good thing to implement the neccessary glue.

      • LWP auto-detects Crypt::SSLeay vs IO::Socket::SSL and does the appropriate thing.

        We actually moved to Crypt::SSLeay because of the timeout issue, but both should work.

        What was the compilation issue?

        -Dom

        • Hhmm, I don't really remember the exact issue. What I do remember is that other people on the net (at least according to google :) seemed o have has similar problems with Crypt::SSLeay, specific archs and the latest version of OpenSSL.
  • I just went through the hassle with Crypt::SSLeay yesterday and wasted a few hours of my life. moving to IO::Socket::SSL solved things perfectly. so, thanks.