> On Wed, 18 Jun 2008 15:18:20 +0100, "Dave Shield" <[EMAIL PROTECTED]>
> said:
>>> We're currently in code freeze for the 5.2.5 release,
>>> so fixing that line may have to wait until after that is out.
>>
>> I'm hereby calling for votes to include this fix (r17048) in 5.2.5.
>>
>> +1
2008/6/17 Thomas Anders <[EMAIL PROTECTED]>:
> Dave Shield wrote:
>> 2008/6/16 Chase Douglas <[EMAIL PROTECTED]>:
>>> I've found the exact same bug ...
>>> but in snmplib/snmpTCPIPv6Domain.c instead of snmplib/snmpUDPIPv6Domain.c.
>>
>> Thanks for the report.
>> I've fixed this in the 5.3.x lines a
Dave Shield wrote:
> 2008/6/16 Chase Douglas <[EMAIL PROTECTED]>:
>> I've found the exact same bug ...
>> but in snmplib/snmpTCPIPv6Domain.c instead of snmplib/snmpUDPIPv6Domain.c.
>
> Thanks for the report.
> I've fixed this in the 5.3.x lines and above.
>
> We're currently in code freeze for th
2008/6/16 Chase Douglas <[EMAIL PROTECTED]>:
> I've found the exact same bug ...
> but in snmplib/snmpTCPIPv6Domain.c instead of snmplib/snmpUDPIPv6Domain.c.
Thanks for the report.
I've fixed this in the 5.3.x lines and above.
We're currently in code freeze for the 5.2.5 release,
so fixing that l
I've found the exact same bug as described here: http://sourceforge.net/mailarchive/forum.php?thread_name=46C64454.9040209%40linux.vnet.ibm.com&forum_name=net-snmp-coders
, but in snmplib/snmpTCPIPv6Domain.c instead of snmplib/
snmpUDPIPv6Domain.c. The following patch solves the buffer overrun: