>>>>> On Sat, 21 Feb 2009 10:36:55 +0000, Dave Shield
>>>>> <[email protected]> said:
DS> if (uptr->cloneFrom == NULL) {
DS> return SNMP_ERR_INCONSISTENTNAME;
...
DS> Wes - can you shed any light on what might be happening here?
Well, that's required by the RFC... you can't set your password if the
user hasn't been cloned from something else.
However, this is sort of different as the user was added externally to
the normal SNMPv3 usm creation process. So I'd suggest we:
1) add a "or storageType == PERMENANT" to it
2) add a "or some other set flag to check" to check if the user came
from external-to-the-mib-creation-process
3) set the internal cloneFrom variable to something when a user is
created from the createUser line.
--
Wes Hardaker
Sparta, Inc.
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
