Re: Running agent without snmpd.conf

On 07/01/2008, Mani, Sathish <[email protected]> wrote:
> I saw that piece of code before sending the email to you, but it looked
> a bit complicated. I was expecting a simpler API.

Why?

The access control mechanism within SNMP is fairly complex,
since it needs to handle two significantly different styles of
authentication (community-based, and user-based).   And in
fact, it has the potential to handle several other different
approaches as well (e.g. Kerberos tickets, etc)


We provide a configuration directive that is straightforward to
use ("rocommunity string"), but that then needs to be converted
into the appropriate settings in the underlying MIB tables.
So the code to handle this is relatively complex.
  Remember that it has to set up the community->security name
mapping, a corresponding group for this name, and the appropriate
access for this group.   All of this needs code.

This code isn't really regarded as part of the user-visible interface.
If an administrator wants to manipulate the access settings,
they'd typically either use the config directives ("rocommunity"),
or work with the MIB tables ("snmpvacm").


But if you want a simple API call, why not simply use

    vacm_parse_rocommunity("rocommunity", "public");


Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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