Hi,
Thank you Menase, Laurent, Craig Small and Magnus Fromreide.
I am using snmp4j as snmp-agent and snmptrapd as trap-receiver. I would
like to know how snmptrapd can be configured to authenticate AES192 of
snmp4j ?
If company develop support for AES192 then how will the generic
snmp-man
On Tue, Feb 18, 2025 at 03:19:27PM +0530, Pushpa Thimmaiah wrote:
> Hi All,
>
> I would like to understand why does oid of AES128 and AES192 not in same
> branch.
> AES128 : .1.3.6.1.6.3.10.1.2.4
> AES192 : .1.3.6.1.4.1.14832.1.3
>
It has to do with timing and processes.
If you look up the OID
Hi Pushpa
According to
http://www.net-snmp.org/wiki/index.php/Strong_Authentication_or_Encryption
1.3.6.1.4.1.14832.1.3 is not supported since not defined by RFC if I read well,
but some other RFC defined OID were defined in rfc7860
Which if I am not wrong are:
snmpUsmHmacSha2MIB
1.3.6.1.2.1.235
