Hi Peter,
SNMP4J uses the full 8bit per byte provided to the passwordToKey method call
as an OctetString passphrase. Thus, no character conversion is done within
SNMP4J. You have thus the full control how your password is converted into
an OctetString (bytes) from a character string.
If you use the OctetString(String) constructor then String.getBytes() is
used
and thus the platforms default characters set is used.
If you want/need to use a different character set, the use the
OctetString(byte[])
constructor instead.
Of course, you will still have to know the character set use by the
agent too,
because both have to match.
Best regards,
Frank
Am 26.03.2014 11:56, schrieb McCarthy, Peter CIV NAWCTSD, 4.6.2.3:
Good morning all,
We have SNMP4J in a production system and I've noticed that using special characters in the
authentication and privacy phrases doesn't seem to work. For example,
"Password12@345678" will fail where "Password12345678" will succeed. My
suspicion is that it is a limitation of the device I'm talking to and not of the SNMP4J library.
Is my assessment correct? Or are there limitations on the character set for pass phrases that are
identified somewhere deep within the SNMP RFCs?
Thanks,
Peter McCarthy
_______________________________________________
SNMP4J mailing list
[email protected]
https://s16675406.onlinehome-server.info/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]
https://s16675406.onlinehome-server.info/mailman/listinfo/snmp4j
