in reply to Re^16: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
in thread ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003

That fixed it. Replace my one line with your if block and: 

C:\Perl510>ppm install http://www.bribes.org/perl/ppm/Crypt-SSLeay.ppd
Downloading Crypt-SSLeay-0.57...done
Unpacking Crypt-SSLeay-0.57...done
Generating HTML for Crypt-SSLeay-0.57...done
Updating files in site area...done
  10 files installed
   7 files updated

[download]

Thanks. Now maybe yeah can get his to work...if he ever comes back and catches up on this thread.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."
  • Comment on Re^17: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
  • Download Code

Replies are listed 'Best First'.
Re^18: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
by yeah (Novice) on Mar 31, 2008 at 03:06 UTC
    Changed the Client.pm file line #41 from 5.008 to 5.010 and ran ppm install 
    ppm install http://www.bribes.org/perl/ppm/Crypt-SSLeay.ppd
MSWin32-x86-multi-thread-5.10Downloading Crypt-SSLeay0.57...done
Unpacking Crypt-SSLeay-0.57...done
Generating HTML for Crypt-SSLeay-0.57...done
Updating files in site area...done
   1 file deleted
   4 files installed
   3 files unchanged
  10 files updated


$ perl testSSL.pl
LWP::UserAgent::new: ()
LWP::UserAgent::request: ()
LWP::UserAgent::send_request: GET https://www.helsinki.fi/
LWP::UserAgent::_need_proxy: Not proxied
LWP::Protocol::http::request: ()
LWP::Protocol::collect: read 495 bytes
LWP::UserAgent::request: Simple response: OK
HTTP/1.1 200 OK
Connection: close
Date: Mon, 31 Mar 2008 03:03:26 GMT
Accept-Ranges: bytes
ETag: "2f4131c-1ef-47a1d157"
Server: Apache
Content-Length: 495
Content-Type: text/html
Last-Modified: Thu, 31 Jan 2008 13:47:03 GMT
Client-Date: Mon, 31 Mar 2008 03:03:26 GMT
Client-Peer: 128.214.205.16:443
Client-Response-Num: 1
Client-SSL-Cert-Issuer: /C=FI/O=Sonera/CN=Sonera Class2 CA
Client-SSL-Cert-Subject: /C=FI/L=Helsinki/O=University of Helsinki/OU=
+IT Department/CN=www.helsinki.fi/emailAddress=webm
aster@helsinki.fi
Client-SSL-Cipher: DHE-RSA-AES256-SHA
Client-SSL-Warning: Peer certificate not verified
Title: University of Helsinki

<html>
<head>
<title>University of Helsinki</title>
</head>

<body>
<h1><a href="http://www.helsinki.fi/yliopisto/">University of Helsinki
+</a></h1>

This is the secure www server
of the University of Helsinki, Administration Office,
<a href="http://www.helsinki.fi/atk/">IT Department</a>.

<P>

Get the HY-CA certificate authority root certificate from
<a href="https://www.helsinki.fi/ca/">https://www.helsinki.fi/ca/</a>.
<P>

<hr>

<address>webmaster@helsinki.fi</address>

</body>
</html>

    [download]
    Everything works just fine now. What a pain in the proverbial bottom. Thanks to all who took the time to look at this. Not sure why Client.pm was wrong but I'm off to the races now!-)
[reply]
[d/l]
Re^18: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
by yeah (Novice) on Mar 30, 2008 at 10:00 UTC
    I figured I'd give it a day or so :o) and I will check the HKEYs and the .def tonight when I'm back at the system. It would be nice for someone to track down the actual cause of this difugalty and make a fix. There is a lot of useless info on google as to the actual fix for this issue. Even more disconcerting is the fact that it workks for some and not for others. Why it things I had multiple versions of Perl on my install target is beyond me. This is the first perl install ever on it.-(
[reply]
      Even more disconcerting is the fact that it workks for some and not for others

      But it's failing for you in a *unique* way. Afaict, you're problem is that Crypt::SSLeay cannot be loaded because the 'boot_Crypt__SSLeay' symbol in c:/Perl/site/lib/auto/Crypt/SSLeay/SSLeay.dll cannot be found. Nobody else has struck that particular problem - and most of this thread has concentrated on discussing something that doesn't affect you.

      It beats me how the 'boot_Crypt__SSLeay' symbol cannot be found ... because, if c:/Perl/site/lib/auto/Crypt/SSLeay/SSLeay.dll *is* the dll from the uwinnipeg PPM package, it clearly exports the 'boot_Crypt__SSLeay' symbol.

      Cheers,
      Rob
[reply]
[d/l]

        Seems to me there were at least 4 problems (and some confusion exacerbated by one or more of those) explored in this thread.

        1. The OPs original problem (RESOLVED?*):

          (*)Had the OP just not attempted to install Crypt::SSLeay at this point? 

          Failed to GET 'https://www.helsinki.fi/': 
501 Protocol scheme 'https' is not supported 
(Crypt::SSLeay not installed) at testSSL.pl line 19.

          [download]
        2. The OP's secondary problem once he installed Crypt::SSLeay(UNRESOLVED*):

          (*)I agree that this error could not have occured if the DLL came from a PPM distribution. What is the OP not telling us? 

          $ perl -MCrypt::SSLeay -e "print 'OK'"
Can't find 'boot_Crypt__SSLeay' symbol 
in c:/Perl/site/lib/auto/Crypt/SSLeay/SSLeay.dll

          [download]
        3. The problem with using PPM from AS1000 (RESOLVED*)

          (*)for AS1000, but the OP apparently had the same problem with AS1002? 

          ppm install http://cpan.uwinnipeg.ca/PPMPackages/10xx/Crypt-SSLeay.ppd
ppm install failed: The PPD does not provide code to install for this 
+platform

          [download]

          Which combined with (differential) displaying by the servers or browsers of the XML contents of PPDs: 

          OpenSSL glue that provides LWP https support 
Joshua Chamas <josh (at) chamas dot com> install_ssl

          [download]
        4. The build failure of Crypt::SSLeay when using the generated makefile (UNRESOLVED): 
          link -out:blib\arch\auto\Crypt\SSLeay\SSLeay.dll 
-dll -nologo -nodefaultlib -debug -opt:ref,icf  
-libpath:"C:\Perl\lib\CORE"  
-machine:x86 SSLeay.obj   
C:\Perl\lib\CORE\perl58.lib 
c:\cl\lib\oldnames.lib c:\cl\lib\kernel32.lib c:\cl\lib\user32.lib 
c:\cl\lib\gdi32.lib c:\cl\lib\winspool.lib c:\cl\lib\comdlg32.lib 
c:\cl\lib\advapi32.lib c:\cl\lib\shell32.lib c:\cl\lib\ole32.lib 
c:\cl\lib\oleaut32.lib c:\cl\lib\netapi32.lib c:\cl\lib\uuid.lib 
c:\cl\lib\ws2_32.lib c:\cl\lib\mpr.lib c:\cl\lib\winmm.lib 
c:\cl\lib\version.lib c:\cl\lib\odbc32.lib c:\cl\lib\odbccp32.lib 
c:\cl\lib\msvcrt.lib 
-def:SSLeay.def
...
blib\arch\auto\Crypt\SSLeay\SSLeay.dll : fatal error LNK1120: 50 unres
+olved externals
NMAKE : fatal error U1077: 'link' : return code '0x460'
Stop.

          [download]

          No mention of the required libraries on the generated build command despite that it knows that they are required: 

          BUILD INFORMATION
================================================
ssl library: OpenSSL 0.9.8 in c:\openssl
ssl header:  openssl/ssl.h
libraries:   -Lc:\openssl\lib -lssleay32 -llibeay32
include dir: -Ic:\openssl\include
================================================

          [download]

          Add to that, the "libpath" switch -Lc:\openssl\lib, won't work with the latest distributions (I don't know about earlier ones) of openssl because the libraries are located in subdirectories below that path. And the libraries themselves have different names.

          But that doesn't explain why neither the (wrong) libpath nor the library names showed up in the generated commands?.

        There's not much more can be done unless the OP starts coming clean about what he had done prior to each of the two problems he had.

        Nor unless the maintainer decides to get involved again.

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom