HI, Well, I guess I need to talk with Wes more about this issue.
I believe that there are several problems with the current SNMPv3 framework, and this just reenforces my beliefs. Wes and I have been working for the last couple of years on coming up with a new security model for SNMP. The current architecture just shows that it forces unnatural coupling of unrelated items. To help with a redesign, what is "this feature", and what aspects of it do you want to preserve? Please describe what problem is being solved, and what are the alternative approaches that you see (even if you find them not as good as what is currently done). On Tue, 14 Jun 2005, Thomas Anders wrote: > David T. Perkins wrote: > > Please, re-engineer snmptrapd to not be a subagent at all!!!!!!!!! > > Besides the notification log MIB we also support to manipulate > snmptrapd's USM userbase via the master agent (SNMP-USER-BASED-SM-MIB > under "snmptrapd" context): > > http://sf.net/mailarchive/forum.php?thread_id=5237305&forum_id=4959 > > I'd certainly object against dropping this feature and am not aware of a > better way to do this. Are you? > > > +Thomas Regards, /david t. perkins ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
