> Well, the real solution would be to have Crypt-SSLeay use
> openssl.. as SSLeay (AFAIK) is unsupported. Furthermore, I
> have had problems
> with SSLeay v .6 to connect out to https sites - so you may
> have difficulties
> even if you get SSLeay v. .6 to work.
Not to mention gettting SSLeay v. .6 to compile at all.
>
> So for now, you might want to use a libwww - Net::SSLeay
> combo for your
> application.
That works like a charm for me, although I've had to force
use of ssl3 only by uncommenting the line
#$Net::SSLeay::ssl_version = 3;
in Net::SSLeay. Otherwise I'd get core dumps on certain sites.
(A bug in s_client in 0.9.0, seen on solaris and linux)
>Having libwww-perl use either Net::SSLeay OR
> Crypto-SSLeay would
> be an extra bonus - you might want to follow this up with the
> libwww-perl list
> ([EMAIL PROTECTED]).
I've seen this wish often in comp.lang.perl.* and on the libwww-perl
list, but so far nobody has done anything ;-) I remember seeing a
post from Gisle Aas[1] that he wasn't going to change anything as
long as it worked for him.
>From looking a bit at the perl code, I think that patching
LWP::Protocol::https to use Net::SSLeay might be easier.
>From looking at the number of requests for updated https support in
libwww, I think it would be worth a bit of work. That said, I know
that I'm not quite the c programmer to do this, but I'll gladly help
out anyone by testing builds on different os'es and etc.
[1] Author of Libwww and Crypt::SSLeay
vh.
Mads Toftum, QDPH
---
"What is the sound of Perl? Is it not the sound of a wall that
people have stopped banging their heads against?"
--Larry Wall in <[EMAIL PROTECTED]>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
