I have an application that provides a thin client that will need to allow
for
manipulating SNMP v3 users for an Net-SNMP agent. This would require
listing
existing users, deleting existing USM, and modifying user security
attributes.
This application also implements an SNMP subagent, so has access to the
running agent through the network connection between them.
This custom application is required to allow via a web interface
administration of
SNMP v3 users, which would mean the addition and deletion of USM users with
security credentials, and modifying credentials of existing users.
What implementation makes the most sense and is less problematic.
I am considering the following:
1. Direct manipulation of the SNMP snmpd.conf files followed by an snmpd
reload.
2. The use of subagent accessible APIs to accomplish this task (if
available).
3. Making sytem calls in my application (such as "net-snmp-create-v3-user"
after stopping the service, then restarting it).
In all of these cases, reloading of snmpd could be by:
1. a workstation reboot,
2. issuing via a system call something like "service snmpd reload", or
3. direct manipulation of the UCD-SNMP-MIB::versionUpdateConfig.0 value
to cause Net-SNMP to reload its configuration without rebooting.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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