RE: Crypt::SSLeay
Ah.. I think I know why I did not see the problem.. On hp-ux, perl 5.8.0 comes inbuilt with Net::SSLeay, and any Net::SSL is satisfied by the Net:SSLeay rather than from Crypt::SSLeay.. Net::SSLeay doesn't have this problem of not initializing the library. -Madhu >-Original Message- >From: Cliff Woolley [mailto:[EMAIL PROTECTED] >Sent: Wednesday, January 29, 2003 6:43 PM >To: [EMAIL PROTECTED] >Subject: Re: Crypt::SSLeay > > > >Figured it out. It was a bug in Crypt::SSLeay ... not sure how it ever >even worked. I'm sending them the following patch: > >--- SSLeay.xs.orig 2002-08-01 17:43:22.0 -0400 >+++ SSLeay.xs 2003-01-29 21:41:17.0 -0500 >@@ -109,6 +109,7 @@ >SSLeay_add_all_algorithms(); >SSL_load_error_strings(); >ERR_load_crypto_strings(); >+ SSL_library_init(); > bNotFirstTime = 1; > } > RAND_seed(buf,sizeof buf); > > >Geeze. Crypt:SSLeay's make test actually passes now, it's amazing. ;) > >--Cliff >
Re: Crypt::SSLeay
On Thu, 30 Jan 2003, William A. Rowe, Jr. wrote: > That's actually sorta sad... are they missing CRYPTO_malloc_init as well? [EMAIL PROTECTED]:../build/Crypt-SSLeay-0.45# grep -i CRYPTO_malloc_init * [EMAIL PROTECTED]:../build/Crypt-SSLeay-0.45# Looks that way, yeah... :) --Cliff
Re: Crypt::SSLeay
That's actually sorta sad... are they missing CRYPTO_malloc_init as well? At 08:42 PM 1/29/2003, Cliff Woolley wrote: >Figured it out. It was a bug in Crypt::SSLeay ... not sure how it ever >even worked. I'm sending them the following patch: > >--- SSLeay.xs.orig 2002-08-01 17:43:22.0 -0400 >+++ SSLeay.xs 2003-01-29 21:41:17.0 -0500 >@@ -109,6 +109,7 @@ >SSLeay_add_all_algorithms(); >SSL_load_error_strings(); >ERR_load_crypto_strings(); >+ SSL_library_init(); > bNotFirstTime = 1; > } > RAND_seed(buf,sizeof buf); > > >Geeze. Crypt:SSLeay's make test actually passes now, it's amazing. ;) > >--Cliff
Re: Crypt::SSLeay
Figured it out. It was a bug in Crypt::SSLeay ... not sure how it ever even worked. I'm sending them the following patch: --- SSLeay.xs.orig 2002-08-01 17:43:22.0 -0400 +++ SSLeay.xs 2003-01-29 21:41:17.0 -0500 @@ -109,6 +109,7 @@ SSLeay_add_all_algorithms(); SSL_load_error_strings(); ERR_load_crypto_strings(); + SSL_library_init(); bNotFirstTime = 1; } RAND_seed(buf,sizeof buf); Geeze. Crypt:SSLeay's make test actually passes now, it's amazing. ;) --Cliff
Re: Crypt::SSLeay
Cliff Woolley wrote: On Wed, 29 Jan 2003, MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: PS : I'm using Perl 5.8 though (I'm not sure if it matters, but I can try on 5.6.1) I'm using Linux, Slackware current, kernel 2.4.20, glibc 2.3.1, openssl 0.9.6h, perl 5.8.0, latest Crypt::SSLeay. I've Mandrake9/linux with updates: libopenssl0.9.7-0.9.7-3mdk libopenssl0.9.7-devel-0.9.7-3mdk openssl-0.9.7-3mdk kernel 2.4.19-16mdksmp. Crypt::SSLeay's "make test" has passed with perl 5.8.0 (with ithreads and without). The build generates the following warning: SSLeay.xs: In function `XS_Crypt__SSLeay__Conn_new': SSLeay.xs:237: warning: passing arg 2 of `SSL_set_info_callback' from incompatible pointer type but it's not a problem, since it's invoked only in the debug mode. Though I can't even start the perl-framework, I get: using Apache/2.1.0-dev (prefork MPM) waiting for server to start: 00:00[Thu Jan 30 10:37:27 2003] [warn] _default_ VirtualHost overlap on port 8534, the first has precedence [Thu Jan 30 10:37:27 2003] [warn] _default_ VirtualHost overlap on port 8535, the first has precedence (98)Address already in use: make_sock: could not bind to address 0.0.0.0:8534 no listening sockets available, shutting down Unable to open logs Do you have the same problem with an updated Apache::Test? __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
RE: Crypt::SSLeay
On Wed, 29 Jan 2003, MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) wrote: > PS : I'm using Perl 5.8 though (I'm not sure if it matters, but I can > try on 5.6.1) I'm using Linux, Slackware current, kernel 2.4.20, glibc 2.3.1, openssl 0.9.6h, perl 5.8.0, latest Crypt::SSLeay. --Cliff
RE: Crypt::SSLeay
I just compiled 0.45 with OpenSSL 0.9.7, and the only error that I'm seeing is : ssl/varlookupok 27/72# Failed test 28 in /tmp/madhum.perl_framework/httpd-test/perl-framework/Apache-Test/lib/Apache/ Test.pm at line 46 fail #28 and I'm not seeing any seg fault type messages in the error_log. -Madhu PS : I'm using Perl 5.8 though (I'm not sure if it matters, but I can try on 5.6.1) >-Original Message- >From: Cliff Woolley [mailto:[EMAIL PROTECTED] >Sent: Wednesday, January 29, 2003 12:50 AM >To: [EMAIL PROTECTED] >Subject: Crypt::SSLeay > > > >Has anybody out there managed to get Crypt::SSLeay to do anything but >segfault with recent OpenSSL's? I sure can't. As a result, >every single >SSL test fails for me. > >--Cliff >
RE: Crypt::SSLeay
I've been using 0.45 with a older version of openssl 0.9.6f - I can try the latest openssl today.. -Madhu -Original Message- From: Cliff Woolley To: [EMAIL PROTECTED] Sent: 1/29/03 12:50 AM Subject: Crypt::SSLeay Has anybody out there managed to get Crypt::SSLeay to do anything but segfault with recent OpenSSL's? I sure can't. As a result, every single SSL test fails for me. --Cliff
