Dave Shield£º

yeah, it really does work, thank you!
        

======= 2006-09-21 16:11:11 =======

>Where did "private" come from?

i had thought the security name is independent from the USM dependent username,
so i construct one from the scratch....

>Because you haven't defined the user "nssro" as part of the group "mygrp".
>You've included a (non-existent?) user "private", but not "nssro"

as above

>should be mapped into a particular security name - which is then used
>for the VACM checks.

yeah, i see, thank you.
security name is a term origining from VACM, and for VACM check.
        when usm, the username is identity to the security name,
        when v1/v2c, we have to map the community to a security name used by 
VACM.

>com2sec has *nothing* to do with USM.  It's purely concerned with
>community-based requests.  (Hence the name - "com" means "community").
>SNMPv3/USM is a completely different administrative structure.
>
>Both SNMPv1/2c and SNMPv3/USM map the local admin information into a
>security name
>(SNMPv1/2c via com2sec, and SNMPv3/USM via the identity mapping on the
>username).
>It's this security name that is then used in the group/access configuration.

thank you, maybe we should gather these explaination into the snmpd.conf(5) 
manual...

= = = = = = = = = = = = = = = = = = = =

¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡        Leo Lei
¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡        2006-09-21



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to