On Tue, 2006-01-24 at 18:32 +0200, Makavy, Erez (Erez) wrote: > 1) usm_process_in_msg() is invoked indirectly by snmpv3_parse(), right?
Yup. The routine 'usm_secmod_process_in_msg' is the 'decode' hook for the User-Based security model. You should be able to trace through from there to usm_process_in_msg without any difficulty. > 2) snmpv3_parse() is called when the PDU's version is 3, > a) so how is the usmUser table accessed when a verision 1 > PDU is processed? I'm not convinced it is. > (after the community name has been converted to a security name) That's the point. The community string is converted to a *security* name, not a *user* name. It's working at an SM-independent level. The usmUserTable is concerned with mapping the USM-specific user name into an (SM-independent) security name. This is easy to overlook, since the security name and user name are typically the same, but they are conceptually different things. But Wes/Robert are the SNMPv3 experts.... Dave ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
