NetAddr::IP

[Bowie Bailey <Bo...@BUC.com>]

At one point there was an issue with the NetAddr::IP package that caused
problems with SA, but I have not heard anything about it recently.  Does
the current 4.037 version still have the same issue?  If so, what needs
to be done to work around it?

I am running the latest SA 3.3.1, if it makes a difference.

Thanks,

-- 
Bowie

Re: NetAddr::IP

[Karsten Bräckelmann <gu...@rudersport.de>]

On Thu, 2010-12-09 at 16:49 -0500, Bowie Bailey wrote:
> On 12/9/2010 4:39 PM, Karsten Bräckelmann wrote:

> > According to that, the bug finally and fully has been fixed since
> > NetAddr::IP 4.036.
> >
> > Always glad to copy-n-paste other guys' Subject lines into search
> > engines or list archives. The latter answered this question. ;)
> 
> Appreciated...  At least you didn't link me to www.lmgtfy.com!  :)

Well, I didn't use google anyway this time. ;)

> I followed the thread when it was active, but there was never anything
> on the thread that indicated that the bug had been fully fixed.  I had
> not looked at the actual bug entry.

I didn't recall all details either, but had a feeling it might be worth
digging it up. Frankly, I thought the patch by Mark I referenced could
help you, but kept digging since that was about a previous release. I
did have a look at the original bug back those days, but that was before
the reopening and subsequent second fix.

On the upside, we now have it all documented here. :)


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

Re: NetAddr::IP

[Bowie Bailey <Bo...@BUC.com>]

On 12/9/2010 4:39 PM, Karsten Bräckelmann wrote:
> On Thu, 2010-12-09 at 16:21 -0500, Bowie Bailey wrote:
>> At one point there was an issue with the NetAddr::IP package that caused
>> problems with SA, but I have not heard anything about it recently.  Does
>> the current 4.037 version still have the same issue?  If so, what needs
>> to be done to work around it?
> You're talking about this thread, in particular one post that shows
> 4.035 still being broken after the first round of fixes.
>   http://markmail.org/message/nwl5lgmmubfeg5y3
>
> Couple posts later in that thread, again a reference to the bug.
>   https://rt.cpan.org/Public/Bug/Display.html?id=62521
>
> According to that, the bug finally and fully has been fixed since
> NetAddr::IP 4.036.
>
> Always glad to copy-n-paste other guys' Subject lines into search
> engines or list archives. The latter answered this question. ;)

Appreciated...  At least you didn't link me to www.lmgtfy.com!  :)

I followed the thread when it was active, but there was never anything
on the thread that indicated that the bug had been fully fixed.  I had
not looked at the actual bug entry.

-- 
Bowie

Re: NetAddr::IP

[Karsten Bräckelmann <gu...@rudersport.de>]

On Thu, 2010-12-09 at 16:21 -0500, Bowie Bailey wrote:
> At one point there was an issue with the NetAddr::IP package that caused
> problems with SA, but I have not heard anything about it recently.  Does
> the current 4.037 version still have the same issue?  If so, what needs
> to be done to work around it?

You're talking about this thread, in particular one post that shows
4.035 still being broken after the first round of fixes.
  http://markmail.org/message/nwl5lgmmubfeg5y3

Couple posts later in that thread, again a reference to the bug.
  https://rt.cpan.org/Public/Bug/Display.html?id=62521

According to that, the bug finally and fully has been fixed since
NetAddr::IP 4.036.

Always glad to copy-n-paste other guys' Subject lines into search
engines or list archives. The latter answered this question. ;)


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}