>>>>> On Tue, 16 Feb 2010 14:45:50 +0000, Dave Shield >>>>> <d.t.shi...@liverpool.ac.uk> said:
DS> This is a local policy decision - it's not inherent in the SNMP protocol. And to make sure you understand completely: You can also configure the VACM to only allow authenticated *and* encrypted packets. Note that the USM/VACM was designed intentionally to allow a user to select at run-time the level of protection they wanted to use. IE, you can have the case where user "joe" is allowed to send stuff either as authNoPriv or authPriv and the message flags would let the user decide "eh, this isn't private information: send it unencrypted" but the next packet to be "mission critical policy information that must be encrypted". The user can be configured to use encryption (for example) but can choose not to use it *IF* the VACM configuration lets him get away with it. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
