Hi Jochen,
I'm using 3DES to test a SNMP agent. Found the implementation of
Priv3DES::extendShortKey() isn't the same as the definition in the Internet
Draft 'Extension to the User-Based Security Model (USM) to Support Triple-DES
EDE.
According to the draft section 2.1, the P2K algorithm
Hi Friends,
I have seen the below post that SNMP4J wont support *3DES encryption.
*http://lists.agentpp.org/pipermail/snmp4j/2007-June/002224.html
Could you please, confirm me.
Also Please comment me, If it is supported, how to avoid
SNMPv3_USM_UNSUPPORTED_SECURITY_LEVEL = 1403 error.
Thanks,
Hi Jochen,
Thanks a lot.
It is working fine :)
From this i got usage on 3DES,AES192,AES256.
Thanks Frank//Chico.
After extracting the source code
cmdjavac -classpath SNMP4J.jar org/snmp4j/security/SecurityProtocols.java
cmdjar uf SNMP4J.jar org/snmp4j/security/SecurityProtocols.class
Hi Frank and schrieb Chico,
Thanks for your input.
Frank, Yes i have seen your input in different mail reply posted at
http://lists.agentpp.org/pipermail/snmp4j/2005-March/000400.html.
Thanks again.
I have downloaded and installed Cryptography Extension (JCE) Unlimited
Strength Jurisdiction
Not sure, but it may be caused by the OIDs of AES192/AES256. In RFC3826,
only AES128 OID has been defined. And it seems that AES192/AES256 are
not defined in the standard MIBs...
So, there may be difference definition between SNMP4J and the other
entity used (e.g CISCO).
Hope that's helpful.
