> 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
Wes Hardaker wrote:
I'd like to propose something like the following. It works already
and I've successfully set up authorization such that I can say
"community xyz is only allowed to log" and "community abc is allowed
to execute", etc.
Not too bad. I'd say let it cook in CVS MAIN and I'll b
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
