Skip Menu |

This queue is for tickets about the Crypt-SSLeay CPAN distribution.

Report information
The Basics
Id: 33998
Status: rejected
Priority: 0/
Queue: Crypt-SSLeay

People
Owner: dland [...] cpan.org
Requestors: hierophant [...] pcisys.net
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in:
  • 0.51
  • 0.57
Fixed in: (no value)



Subject: Connect failures Crypt::SSLeay 0.57 + LWP 1.11
I get various connection errors, LWp reports as variously "SSL read failed", "SSL negotiation failed" and as a generic timeout. This appears to be happening only with the following site/URL: https://www.clickrewards.com/statement/statement.html Not that I can get the page with no problem using wget. I was using version 0.51, I upgraded to 0.57 (by the way, had to force install as a/the connect test failed, but it works anyway). Don't know about versions in between. My system: Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 i686 i686 i386 GNU/Linux Perl 5.8.0, openssl 0.9.7 I would really appreciate a fix, as this error is effecting my system and becoming a problem. I understand it is likely an issue with the site itself, but don't know why this effects only Crypt::SSLeay. Thank you.
On Tue Mar 11 16:44:22 2008, hierophant wrote: Show quoted text
> I get various connection errors, LWp reports as variously "SSL read > failed", "SSL negotiation > failed" and as a generic timeout. This appears to be happening only > with the following > site/URL: https://www.clickrewards.com/statement/statement.html > > Not that I can get the page with no problem using wget. > > I was using version 0.51, I upgraded to 0.57 (by the way, had to force > install as a/the > connect test failed, but it works anyway). Don't know about versions > in between.
The test failure is because it attempts to bind to localhost:443 which is apparently in use on your system. I'm planning to fix this in the next release. Show quoted text
> My system: Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 > i686 i686 i386 > GNU/Linux > > Perl 5.8.0, openssl 0.9.7 > > I would really appreciate a fix, as this error is effecting my system > and becoming a problem. I > understand it is likely an issue with the site itself, but don't know > why this effects only > Crypt::SSLeay.
Thanks for the report. Can you create an absolute barebones script that demonstrates the problem? Regards, David
Subject: Re: [rt.cpan.org #33998] Connect failures Crypt::SSLeay 0.57 + LWP 1.11
Date: Mon, 24 Mar 2008 10:22:12 -0600
To: <bug-Crypt-SSLeay [...] rt.cpan.org>
From: Keary Suska <hierophant [...] pcisys.net>
on 3/24/08 5:09 AM, bug-Crypt-SSLeay@rt.cpan.org purportedly said: Show quoted text
> > <URL: http://rt.cpan.org/Ticket/Display.html?id=33998 > > > On Tue Mar 11 16:44:22 2008, hierophant wrote:
>> I get various connection errors, LWp reports as variously "SSL read >> failed", "SSL negotiation >> failed" and as a generic timeout. This appears to be happening only >> with the following >> site/URL: https://www.clickrewards.com/statement/statement.html >> >> Not that I can get the page with no problem using wget. >> >> I was using version 0.51, I upgraded to 0.57 (by the way, had to force >> install as a/the >> connect test failed, but it works anyway). Don't know about versions >> in between.
> > The test failure is because it attempts to bind to localhost:443 which > is apparently in use on your system. I'm planning to fix this in the > next release.
Yes, this is the case for this machine. I had no problem on my desktop, which doesn't have anything listening on 443. Show quoted text
>> My system: Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 >> i686 i686 i386 >> GNU/Linux >> >> Perl 5.8.0, openssl 0.9.7 >> >> I would really appreciate a fix, as this error is effecting my system >> and becoming a problem. I >> understand it is likely an issue with the site itself, but don't know >> why this effects only >> Crypt::SSLeay.
> > Thanks for the report. Can you create an absolute barebones script that > demonstrates the problem?
Attached. Note that you may have to hit the get statement 2 or 3 times for it to fail. Usually, it is right off the bat. The post fails most often. In any case, the script shows the behavior I am seeing. Thanks, Keary Suska

Message body is not shown because sender requested not to inline it.

Hello: I am going to reluctantly close this bug because the there doesn't seem to be a web site at clickrewards.com. Also, note that the test script contains syntax errors. If you encounter other connection problems with the most up-to-date developer release, please open a new ticket. Thank you. -- Sinan On Mon Mar 24 12:23:48 2008, hierophant wrote: Show quoted text
> on 3/24/08 5:09 AM, bug-Crypt-SSLeay@rt.cpan.org purportedly said: >
> > > > <URL: http://rt.cpan.org/Ticket/Display.html?id=33998 > > > > > On Tue Mar 11 16:44:22 2008, hierophant wrote:
> >> I get various connection errors, LWp reports as variously "SSL read > >> failed", "SSL negotiation > >> failed" and as a generic timeout. This appears to be happening only > >> with the following > >> site/URL: https://www.clickrewards.com/statement/statement.html > >> > >> Not that I can get the page with no problem using wget. > >> > >> I was using version 0.51, I upgraded to 0.57 (by the way, had to force > >> install as a/the > >> connect test failed, but it works anyway). Don't know about versions > >> in between.
> > > > The test failure is because it attempts to bind to localhost:443 which > > is apparently in use on your system. I'm planning to fix this in the > > next release.
> > Yes, this is the case for this machine. I had no problem on my desktop, > which doesn't have anything listening on 443. >
> >> My system: Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 > >> i686 i686 i386 > >> GNU/Linux > >> > >> Perl 5.8.0, openssl 0.9.7 > >> > >> I would really appreciate a fix, as this error is effecting my system > >> and becoming a problem. I > >> understand it is likely an issue with the site itself, but don't know > >> why this effects only > >> Crypt::SSLeay.
> > > > Thanks for the report. Can you create an absolute barebones script that > > demonstrates the problem?
> > Attached. Note that you may have to hit the get statement 2 or 3 times for > it to fail. Usually, it is right off the bat. The post fails most
often. In Show quoted text
> any case, the script shows the behavior I am seeing. > > Thanks, > > Keary Suska >
Subject: Re: [rt.cpan.org #33998] Connect failures Crypt::SSLeay 0.57 + LWP 1.11
Date: Sun, 15 Aug 2010 09:22:54 -0600
To: bug-Crypt-SSLeay [...] rt.cpan.org
From: Keary Suska <hierophant [...] pcisys.net>
On Aug 14, 2010, at 9:32 PM, A. Sinan Unur via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=33998 > > > Hello: > > I am going to reluctantly close this bug because the there doesn't seem > to be a web site at clickrewards.com. > > Also, note that the test script contains syntax errors. > > If you encounter other connection problems with the most up-to-date > developer release, please open a new ticket.
Thank you for your attention to this. I have not encountered the problem with any other site as of yet, so it may simply have had to do with the site in question, which as you indicate, is no longer active. Show quoted text
> On Mon Mar 24 12:23:48 2008, hierophant wrote:
>> on 3/24/08 5:09 AM, bug-Crypt-SSLeay@rt.cpan.org purportedly said: >>
>>> >>> <URL: http://rt.cpan.org/Ticket/Display.html?id=33998 > >>> >>> On Tue Mar 11 16:44:22 2008, hierophant wrote:
>>>> I get various connection errors, LWp reports as variously "SSL read >>>> failed", "SSL negotiation >>>> failed" and as a generic timeout. This appears to be happening only >>>> with the following >>>> site/URL: https://www.clickrewards.com/statement/statement.html >>>> >>>> Not that I can get the page with no problem using wget. >>>> >>>> I was using version 0.51, I upgraded to 0.57 (by the way, had to force >>>> install as a/the >>>> connect test failed, but it works anyway). Don't know about versions >>>> in between.
>>> >>> The test failure is because it attempts to bind to localhost:443 which >>> is apparently in use on your system. I'm planning to fix this in the >>> next release.
>> >> Yes, this is the case for this machine. I had no problem on my desktop, >> which doesn't have anything listening on 443. >>
>>>> My system: Linux 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 >>>> i686 i686 i386 >>>> GNU/Linux >>>> >>>> Perl 5.8.0, openssl 0.9.7 >>>> >>>> I would really appreciate a fix, as this error is effecting my system >>>> and becoming a problem. I >>>> understand it is likely an issue with the site itself, but don't know >>>> why this effects only >>>> Crypt::SSLeay.
>>> >>> Thanks for the report. Can you create an absolute barebones script that >>> demonstrates the problem?
>> >> Attached. Note that you may have to hit the get statement 2 or 3 times for >> it to fail. Usually, it is right off the bat. The post fails most
> often. In
>> any case, the script shows the behavior I am seeing. >> >> Thanks, >> >> Keary Suska >>
> > >
Keary Suska (719) 473-6431 (719) 440-9952 (cell)