Argus 3.0.5.35 bug

[Carter Bullard]

Hey Michael,
This bug, I believe, involved passing a buffer to the wrong IP address decoder/printer, where we told the routine that the address was an IPv4 address, when it was really an IPv6 address.  The bit that indicated that it was IPv6 was masked off by mistake.  Argus has routines to print dozens of different types of network addresses, and like the OS, the routines don’t have much internal checking to verify the address type.  Pass the routine a buffer, and it will decode the binary based on the type you specify.  So you have to do some work to assure that the printer routine is appropriate for the address that is in the buffer you pass.  Seems that the bug was a typo in this case.

Hope this is helpful ...

Carter

> On Oct 10, 2017, at 5:53 AM, Michael Brookes <mgsb81 at gmail.com> wrote:
> 
> Hi
> 
> Strange one this, in a mailing post on 19 March 2012 a user describes a bug where a link local ipv6 address is being represented by an ipv4 address of 0.0.128.254.
> 
> I'm interested to know what this bug was and more generally how the v4 address was determined.
> 
> The post is here: http://thread.gmane.org/gmane.network.argus/8405 <http://thread.gmane.org/gmane.network.argus/8405>
> 
> Many thanks
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20171010/d64eebef/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4045 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20171010/d64eebef/attachment.bin>