One thing I was curious about is that if the example (recommended?)
default configuration given in the RFCs specifies an "initial" user with
what is effectively a read-write "internet" view and a read-only
"restricted" view, why hasn't this problem been spotted before? As far
as I can tell, if someone tried to use this configuration, they would
find they could not do any SNMP SETs.
Regards,
Adam.
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Net-snmp-users mailing list
Net-snm...@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
if (send && sess->paramName) {
int filter = _checkFilter(sess->paramName, template_pdu);
if (filter)
send = 0;
}
Because this is contained within the for loop which processes all target
sessions:
for (sptr = sess; sptr; sptr = sptr->next)
I suspect the code should be:
if (send && sptr->paramName) {
int filter = _checkFilter(sptr->paramName, template_pdu);
if (filter)
send = 0;
}
If not then I'm not sure what the code is trying to do.
Regards,
Adam.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev