Ed Fair
writes:
> I'm trying to understand the extended session API, as documented in
> snmp_api.h. These
> three functions require an netsnmp_transport_s*. How can I initialize this
> structure?
You can get the transport from your session handle using snmp_sess_transport().
For
example
Denis Hainsworth wrote:
> Dug into this some more. I see whats happening and not sure if its a bug per
> se but
> I do agree that if there is a non-buggy trap sender its all working properly
> so will
> close the bug with some comments.
I have added some comments to bug #2899 and uploaded the p
Denis Hainsworth wrote:
> #2899 - snmptrap bug
> #2900 - snmptrapd bug
>
> -denis
Denis,
Sorry for the delayed response. I haven't had time to look at this until
recently.
Regarding the snmptrapd bug you created (#2900): I think this is working as
expected.
I compiled and tested v5.7.3 from
Denis Hainsworth wrote:
>
> Thanks Drew! Yeah it seems fix snmptrap which was my primary
> concern.
> -denis
Denis,
If you want this fixed in the net-snmp baseline code, I suggest you open an
issue on the sourceforge page at: https://sourceforge.net/p/net-snmp/bugs/
If you create a bug r
> From: Denis Hainsworth
> Sent: Tuesday, October 30, 2018 7:57 AM
> To: net-snmp-coders@lists.sourceforge.net
> Subject: EXTERNAL: Re: 5.7.3 | snmptrap not populating EngineBoots or
> EngineTime for snmp v3 traps
>
> Just a note to anyone that might run into this. I was interested in all the
You can download the 5.5.2 source code here:
https://sourceforge.net/projects/net-snmp/files/net-snmp/5.5.2/
-Drew
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
I searched for usage of EVP_MD_CTX_free()/EVP_MD_CTX_new() and found a similar
memory leak in the generate_Ku() function within snmplib/keytools.c. I had to
craft up a client app to force this error path, but Valgrind did confirm it:
==4091== 17,328 bytes in 361 blocks are definitely lost in
I found a memory leak in the sc_hash()/sc_hash_type() function within
snmplib/scapi.c. The leak was identified by running Valgrind on a SNMP client
application which queries v3 servers using SHA/AES.
Here's an example of the Valgrind memory leak trace (using net-snmp-5.7.2-28
from RHEL7):
==1
I have identified a memory leak (and the corresponding fix) within the net-snmp
library code.
Should I just submit a bug report on Sourceforge and include the patch, or is
there some other method that is preferable?
Thanks
-Drew
___
Net-snmp-coders
