What would cause SSL requests to segfault

What would cause SSL requests to segfault

am 14.06.2006 02:14:27 von ML

Hi,

I'm trying to use the example of :

lwp-request https://www.nodeworks.com


When it segfaults. I've tried to re-install a few things like
openssl (Version 0.9.8b_1), Crypt::SSLeay (Version 0.51) and
libwww (Version 5.805). But I still get it.

It seems to show via a backtrace :

#0 0x2833029d in SSL_CTX_ctrl () from /usr/local/lib/libssl.so.4
#1 0x28302798 in XS_Crypt__SSLeay__CTX_new ()
from /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Crypt/SSLeay/ SSLeay.so

Any ideas what to do?

Thanks, Tuc

Re: What would cause SSL requests to segfault

am 14.06.2006 08:49:11 von jansen

Probably it=B4s related to
http://rt.cpan.org/Public/Bug/Display.html?id=3D16735

heiko

Am Mittwoch, 14. Juni 2006 02:14 schrieb Tuc at T-B-O-H =20
[What would cause SSL requests to segfault]:

> Hi,
>
> I'm trying to use the example of :
>
> lwp-request https://www.nodeworks.com
>
>
> When it segfaults. I've tried to re-install a few things like
> openssl (Version 0.9.8b_1), Crypt::SSLeay (Version 0.51) and
> libwww (Version 5.805). But I still get it.
>
> It seems to show via a backtrace :
>
> #0 0x2833029d in SSL_CTX_ctrl () from /usr/local/lib/libssl.so.4
> #1 0x28302798 in XS_Crypt__SSLeay__CTX_new ()
> from
> /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Crypt/SSLeay/ SSLeay.so
>
> Any ideas what to do?
>
> Thanks, Tuc

Re: What would cause SSL requests to segfault

am 14.06.2006 19:29:21 von ML

>
> Probably it´s related to
> http://rt.cpan.org/Public/Bug/Display.html?id=16735
>
Um... :-/ Probably. I didn't think to mention about the
compiler warnings... Some packages are fine having them.

I did the change mentioned (all to ssl), recompiled (Got
pretty much the same warnings) , reinstalled and now it works!

Is this going to be in a new version soon? Or should I submit
a fix to the FreeBSD ports for now?

Thanks, Tuc
> heiko
>
> Am Mittwoch, 14. Juni 2006 02:14 schrieb Tuc at T-B-O-H
> [What would cause SSL requests to segfault]:
>
> > Hi,
> >
> > I'm trying to use the example of :
> >
> > lwp-request https://www.nodeworks.com
> >
> >
> > When it segfaults. I've tried to re-install a few things like
> > openssl (Version 0.9.8b_1), Crypt::SSLeay (Version 0.51) and
> > libwww (Version 5.805). But I still get it.
> >
> > It seems to show via a backtrace :
> >
> > #0 0x2833029d in SSL_CTX_ctrl () from /usr/local/lib/libssl.so.4
> > #1 0x28302798 in XS_Crypt__SSLeay__CTX_new ()
> > from
> > /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Crypt/SSLeay/ SSLeay.so
> >
> > Any ideas what to do?
> >
> > Thanks, Tuc
>

Re: What would cause SSL requests to segfault

am 16.06.2006 09:08:24 von jansen

Am Mittwoch, 14. Juni 2006 19:29 schrieb Scott "Tuc" Ellentuch at=20
T-B-O-H [Re: What would cause SSL requests to=20
segfault]:

> Is this going to be in a new version soon? Or should I submit
> a fix to the FreeBSD ports for now?

I have no idea if there will be a fixed version on CPAN. I tried to=20
contact the original implementor/maintainer of Crypt::SSLeay on this=20
problem about 3 months ago, but didn=B4t receive any response.
I think I saw some info about a non-maintainer-upload on CPAN but you=20
should verify that.
Regarding FreeBSD: I=B4m using Linux or Solaris and have no idea how=20
=46reeBSD ports work ;-)

heiko

Re: What would cause SSL requests to segfault

am 26.06.2006 11:32:39 von alan.gibson

is anyone working on getting this fix into cpan? given the importance
of Crypt::SSLeay, this is a serious problem. if no one is already
working on it, im willing to give it a go.

alan

On 6/16/06, Heiko Jansen wrote:
> Am Mittwoch, 14. Juni 2006 19:29 schrieb Scott "Tuc" Ellentuch at
> T-B-O-H [Re: What would cause SSL requests to
> segfault]:
>
> > Is this going to be in a new version soon? Or should I submit
> > a fix to the FreeBSD ports for now?
>
> I have no idea if there will be a fixed version on CPAN. I tried to
> contact the original implementor/maintainer of Crypt::SSLeay on this
> problem about 3 months ago, but didn=B4t receive any response.
> I think I saw some info about a non-maintainer-upload on CPAN but you
> should verify that.
> Regarding FreeBSD: I=B4m using Linux or Solaris and have no idea how
> FreeBSD ports work ;-)
>
> heiko
>
>