On 16 February 2011 17:03, Ashwin Kumar <[email protected]> wrote: > Please add rocommunity and rwcommunity strings in your snmpd.conf. > It must look like > rocommunity public > rwcommunity private
Please do *NOT* suggest configuring a read-write community of "private". If you must use SET with community-based versions of SNMP, then at the very least you should use a secret community name. (Though even this is open to packet sniffing). In general, if you are going to use SET requests, then you should be looking at SNMPv3. But using a "well known" community string for SET requests is just asking for trouble - akin to having user accounts with no password! This is a Very Bad Idea. Please do not do this, or suggest that anyone else does this either. Dave ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ 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
