Hi,
The SNMPv3 USM uses localized users on the wire. That's why you cannot
see the any difference. Even for a "non-localized" user in SNMP4J, a
localized
will be created internally in the USM (on-the-fly).
Besgt regards,
Frank
Am 12.03.2013 02:53, schrieb m k:
Hello,
I have a confusion I'd like to clear up about localization. So, if I understand
correctly, these should be the results when adding a user according
to different function signatures:
usm.addUser(user.getSecurityName(), usm.getLocalEngineID(), user); <-- User is
localized (password + engine + algorithm = key)
usm.addUser(user.getSecurityName(), null, user) <-- Not localized ? (password
+ algorithm = key)
usm.addUser(user.getSecurityName(), user) <-- Not localized ? (password +
algorithm = key)
....
However, I'm confused, because I have tried to add the user in all these ways,
but I never have to change this command:
"snmpget -v 3 -u MYUSER -l authPriv -a SHA -A MYUSERAuthPassword -x DES -X
MYUSERPrivPassword localhost:1161 .1.3.6.1.2.1.1.1.0"
The command ALWAYS works. I would think that I should need to change some
parameter or something to indicate that I'm using a localized key or
non-localized key, but I don't.
Is there some logic going on behind the scenes on the manager side or SNMP4j
side to make this work somehow?
Thanks
_______________________________________________
SNMP4J mailing list
[email protected]
http://lists.agentpp.org/mailman/listinfo/snmp4j
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
_______________________________________________
SNMP4J mailing list
[email protected]
http://lists.agentpp.org/mailman/listinfo/snmp4j
