HI, Well, I certainly disagree with this! If the security level is "noAuthNoPriv" then I believe that notifications should be "accepted", but put in a "different" pile. For notifications with security level of "authNoPriv" (and even "authPriv") where there is no user, the "keys don't match", or the "clocks don't match", I believe that they should be put in yet another pile.
My motivation is that I believe that most of the time that the "unacceptable" notifications are due to misconfiguration of configuration data and not due to an attack, and the save information is both useful in fixing the misconfiguration and have useful "event information". On Tue, 29 Nov 2005, Wes Hardaker wrote: > >>>>> On Tue, 29 Nov 2005 12:07:02 -0500, Robert Story <[EMAIL PROTECTED]> > >>>>> said: > > Robert> - snmptrapd will no longer accept all traps by default. It > Robert> must be configured with acceptable SNMPv1/v2c community > Robert> strings and/or SNMPv3 authentication parameters. Non > Robert> authenticated traps/informs will be dropped. > > acceptable -> authorized > SNMPv3 authentication parameters -> SNMPv3 users > non authenticated -> non-authorized. > > -- > Wes Hardaker > Sparta, Inc. Regards, /david t. perkins ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
