[erlang-questions] SNMPv3 AES Auth Fix

[Daniel Goertzen]

Github says the last work done in that part of the code was 2013, so no.
SNMPv3 agent does work (I use it), but it looks like the manager is still
picking the wrong engineid/boots.

https://github.com/erlang/otp/commits/master/lib/snmp/src/manager/snmpm_usm.erl



On Tue, 10 Apr 2018 at 15:25 Samuel Warters <samwar@REDACTED> wrote:

> The project I work on does extensive SNMPv2c reads from network devices,
> as part of a PCI requirement, we need to migrate to using SNMPv3. While
> researching the upgrade path, I stumbled upon this mailing list post:
> http://erlang.org/pipermail/erlang-questions/2017-June/092546.html, which
> basically states AES auth is broken.
>
> Having AES encryption/authentication is a must as many network devices use
> it. I was wondering has the AES auth fix ever gone out in an official OTP
> release? Looking at the main OTP source, It doesn't look like it, but I
> wanted to confirm.
>
> Thanks.
> ---
> Sam
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180411/7f799d56/attachment.htm>