On Fri, 17 Apr 2020 12:32:15 -0400 Wilfried Teiken <wtei...@teiken.org>
wrote:
>
> Dear Maintainer,
Hello Wilfried,
>
> when configuring SNMP as v3 with privacy enabled and "privProtocol =
AES" in
> /etc/nut/ups.conf for the UPS then the communication with the UPS
will fail.
>
> The sympton is that on startup the driver will report:
> - "Unknown mibs value: apcc" (with "mibs = apcc")
> - "No supported device detected" (with "mibs = auto"
>
> Communication with "privProtocol = DES" works if the SNMP endpoint is
configured
> accordingly, so this only affects the "AES" setting.
>
> The underlying root cause is a length issue for the 'usmAESPrivProtocol'
> oid value, causing the wrong privacy string being passed into the
net-snmp
> library caused by a #define that is leading to a sizeof() with a pointer
> instead of the oid array.
>
> See attached patch for a fix.
Could you please tell me if you are still experiencing this issue with
the version 2.8.0 that is currently in debian unstable?
I can see that the code to detect
usmAESPrivProtocol/usmAES128PrivProtocol availability has changed.
Also, in the build logs of version 2.7.14, I can see the compiler
complain about the size of these types, while this warning is not
present in version 2.8.0
I think that this is now fixed.
Could you please confirm?
Kind regards,
Laurent Bigonville
