Re: The problem of allowing a cooomunity or usmUser to belong to multiple group
Dave Shield <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 15 March 2010 19:02, Fatima Peter <[email protected]> wrote: > I have a question on vacm group and whether the same communitystring or > usmUser can belong to multiple groups. Probably not. Looking at the vacmSecurityToGroupTable (in SNMP-VIEW-BASED-ACM-MIB) the table is indexed by the pair (securityModel, securityName), and defines a mapping from this to a (single) security group. So a given security name can only belong to one group. The security name is not quite the same as the usmUserName or the community string, but that is still a clearly defined mapping. So a given username/community will always be converted into a single security name, and hence part of just one group. > For example let us say we have a community string "public" which is > configured to belong to 2 groups "v1Group1" and "v1Group2". > > com2sec test 10.10.0.0/16 public > > group v1Group1 v2c test > group v1Group2 v2c test My guess is that the first mapping (into v1Group1) will be applied, and the second one ignored. But suck it and see.... Dave ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ 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