RE: Silvercreek issue

The only issue I am aware of is the one where the length is > 128.

I think Silvercreek does a lot of "negative" testing and I guess expects
an agent to respond in a certain way. In this case they expect the agent
to see that the number is > 128 and handle it not as though it was 0.


-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Dave Shield
Sent: Wednesday, July 28, 2010 11:02 AM
To: Joan Landry
Cc: [email protected]
Subject: Re: Silvercreek issue

On 28 July 2010 15:48, Joan Landry <[email protected]>
wrote:
> I am able to reproduce this problem using any value over 128 as the
> length of the sub identifier of an Octet String:

The maximum length of a valid OID is 128.
Anything longer than that is simply not legitimate.

I was actually asking about your other error report - getting the wrong
rows when the value of individual subidentifiers is/isn't affected by
32-bit wrapping   (but where the OID length is less than 128)

Dave

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users