Dave> If we're going to do this, then let's Do It Right. Wes> There's actually no reason why we can't use this as a temp solution Wes> and then later do the right thing either.
Apart from the fact that this "solution" stinks! :-) (And temporary solutions have a tendency to become permanent) Wes> I don't think we should let 5.3 Wes> go out without something in place. OK - so let's apply the notifyView in (almost) the way it's meant to be used - filtering the incoming snmpTrapOID. That doesn't have quite the flexibility of your three-way shoehorn, but it'll provide a certain level of protection. And it's at least in keeping with the spirit of the VACM RFC, rather than trampling all over it with hobnail boots! Dave ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
