Re: access control
"Dave Shield" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
On 21/02/2008, Mike Ayers <[email protected]> wrote: > > com2sec cust1_sec 192.168.55.0/24 public > > com2sec cust2_sec 192.168.56.0/24 public > > > Note that the community "public" will now have acces to both > cust1_sec rights and cust2_sec rights, so customers 1 and 2 > can see each other's data. Are you sure about that, Mike? Presumably customer 1 will be coming in from the network 192.168.55.x so will be mapped to the internal user "cust1_sec", and hence given access to the 'cust1_v' view. Similarly for customer 2 (on network 192.168.56.x) and the 'cust2_v' view. That relies on the two customers sticking to their own networks, of course, but I believe this setup should provide the separation that Masoud is looking for. Disclaimer: I haven't actually tested this, so I Could Be Wrong. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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