On Mon, 2005-09-05 at 09:12 -0700, Wes Hardaker wrote:
> 99.9% of the time people want to do that is because they want to do
> something that contexts let you do or that VACM already lets you do.
> Find a case where this isn't true ;-)
DisMan :-)
Dave
-
> On Mon, 05 Sep 2005 11:50:43 +0100, Dave Shield <[EMAIL PROTECTED]> said:
>> 0) protocol (SNMP, AgentX, SMUX, internal callback, etc)
>> 1) protocol type (v1, v2c, v3)
>> 2) security model (comm(v1,v2c), usm, etc)
>> 3) security level
>> 4) security name
Dave> Yes - the attributes of the re
On Sat, 2005-09-03 at 11:16 -0700, David T. Perkins wrote:
> But back to the fundamental question...
> Should the semantics associated with objects be allowed to
> use attributes of an SNMP request, and if so, how are these
> attributes passed to access functions?
> Attributes include:
0)
> On Sat, 3 Sep 2005 11:16:45 -0700 (PDT), "David T. Perkins" <[EMAIL
> PROTECTED]> said:
David> Wes - unfortunately, there are some MIB definitions that follow
David> the design pattern of using the security name from the SET
David> operation to do security semantics.
Yep, and I know yo
HI,
Wes - unfortunately, there are some MIB definitions that follow
the design pattern of using the security name from the SET
operation to do security semantics. For example, the access
function for object usmUserOwnAuthKeyChange must have knowledge
of the security name in the SET operation.
The
> On Wed, 27 Jul 2005 10:06:08 +0530, <[EMAIL PROTECTED]> said:
[sorry for the late response]
kanda> I have to get the V3 username of the manager who is sending
kanda> get/set request for pariticular OID in mib2c generated code for
kanda> that OID.
You should never do that ;-)
Seriously. Y
Title: getting v3 user name and community string in mib2c code
Hi
I have to get the V3 username of the manager who is sending get/set request for pariticular OID in mib2c generated code for that OID.
In case of V2 or V1 query i have to get the community string of the
