Over the last month or so, I've applied a number of patches
to the 5.3.x branch and above. Some of these would be
suitable for 5.2.x as well, but I held off applying them
due to the imminent release of 5.2.5. Given that we're
spinning at 5.2.5.rc2 anyway, it's worth considering whether
any of these should be included as part of that.
The relevant changes are as follows:
a) snmplib/parse.c
Extend DESCRIPTION/REFERENCE buffers
to handle longer strings. (SVN revisions 16876/7)
b) snmplib/snmp_api.c
Don't create null-length users
(SVN revision 16908)
c) snmplib/snmp_api.c
Ensure all protocol IDs are unsigned 32 bit
(SVN revision 16971)
d) snmplib/asn1.c
Better handling of OID parse failure
(SVN revision 16956)
e) agent/mibgroup/host/hr_filesys.c
Recognise NFS4 mounts
(SVN revision 16957)
f) agent/mibgroup/agentx/{master,subagent}.c
Fix memory leak
(SVN revisions 16972/3)
g) dist/*-init.d
Handle empty /etc/sysconfig/network file
(SVN revision 16958)
h) various
Assorted missing error checks
(SVN revision 16979)
Of these, items b) & h) could potentially crash the agent in
certain circumstances - b) is known to do so given a suitable
(mis-)configuration, h) may only be a theoretical risk.
The others are simply tweaking various aspects of behaviour.
I'd like to call for an indication of which of these
should/should not be applied to the 5.2.x line, ready
to be included in the 5.2.5 release.
Dave
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
