Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Bencode CPAN distribution.

Report information
The Basics
Id: 29630
Status: rejected
Priority: 0/
Queue: Bencode

People
Owner: Nobody in particular
Requestors: btjunkie [...] btjunkie.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Bdecode bug
Date: Thu, 27 Sep 2007 01:19:58 +0200
To: bug-bencode [...] rt.cpan.org
From: BTJunkie <btjunkie [...] btjunkie.org>
Greetings, I've noticed a flaw that causes bdecode to lock up completely. It's just malformed data within due to an http error on a scrape file, but it causes it to lock. I've attached the scrape file to this e-mail, to see for yourself just try to bdecode it!
Download scrape
application/octet-stream 29k

Message body not shown because it is not plain text.

Subject: Re: [rt.cpan.org #29630] AutoReply: Bdecode bug
Date: Thu, 27 Sep 2007 01:46:03 +0200
To: bug-Bencode [...] rt.cpan.org
From: BTJunkie <btjunkie [...] btjunkie.org>
Sorry, please disregard. I forgot that I already editted the code and commented out some of the croak statements... Bugs in Bencode via RT wrote: Show quoted text
> Greetings, > > This message has been automatically generated in response to the > creation of a trouble ticket regarding: > "Bdecode bug", > a summary of which appears below. > > There is no need to reply to this message right now. Your ticket has been > assigned an ID of [rt.cpan.org #29630]. Your ticket is accessible > on the web at: > > http://rt.cpan.org/Ticket/Display.html?id=29630 > > Please include the string: > > [rt.cpan.org #29630] > > in the subject line of all future correspondence about this issue. To do so, > you may reply to this message. > > Thank you, > bug-Bencode@rt.cpan.org > > ------------------------------------------------------------------------- > Greetings, > > I've noticed a flaw that causes bdecode to lock up completely. It's just > malformed data within due to an http error on a scrape file, but it > causes it to lock. I've attached the scrape file to this e-mail, to see > for yourself just try to bdecode it! > > > >
So the problem was not in the module and I can ignore the request? I assume the answer is yes, so I am marking this bug “rejected”; if that’s correct you don’t need to reply. If there’s still an issue I need to address, please reply and explain and I’ll do what I can.