Yes, I can use wget on our own https site. I built curl 7.21.0 with openssl 1.0.0a and it does not have any problems:
curl -L "https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref"; This goes and gets the file. I thought that I could configure pca to use curl instead of wget, but I didn't find it. Jeff Earickson On Fri, Jul 23, 2010 at 9:16 AM, Alexander Skwar <[email protected]> wrote: > Are you able to make wget connect to other ssl / https enabled sites? > > Alexander > > Am 23.07.2010 um 14:49 schrieb Jeff Earickson <[email protected]>: > >> Gang, >> >> I am trying to get my Solaris 10 boxes upgraded to openssl 1.0.0.a. >> I've had success with >> everything so far, except for wget 1.12 -- which cripples pca. >> >> I have compiled openssl, perl 5.12.1, and wget with Sun's C compiler >> Sun C 5.10 SunOS_sparc Patch 141861-05 2010/04/28. >> >> wget seems to pass all of its checks ok. But this is what I get when >> I try to use pca with this >> wget: >> >> + /usr/local/bin/wget -d --progress=dot:binary >> https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref >> --ca-certificate=/usr/local/adm/pca -O /var/tmp/patchdiag.xref >> Setting --progress (progress) to dot:binary >> Setting --ca-certificate (cacertificate) to /usr/local/adm/pca >> Setting --output-document (outputdocument) to /var/tmp/patchdiag.xref >> DEBUG output created by Wget 1.12 on solaris2.10. >> >> --2010-07-23 08:49:00-- >> https://sunsolve.sun.com/pdownload.do?target=patchdiag.xref >> Resolving sunsolve.sun.com... 192.18.108.40 >> Caching sunsolve.sun.com => 192.18.108.40 >> Connecting to sunsolve.sun.com|192.18.108.40|:443... connected. >> Created socket 4. >> Releasing 0x0008c3f0 (new refcount 1). >> Initiating SSL handshake. >> SSL handshake failed. >> Closed fd 4 >> Unable to establish SSL connection. >> >> Any suggestions? >> >> Jeff Earickson >> Colby College >> > >
