This is a discussion on Re: undocumented config tokens within the SNMP Coders forums, part of the Networking and Network Related category; Quoting myself: > Thanks. I've updated the patch according to your comments: > > http://sourceforge.net/support/tracker....
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Quoting myself:
> Thanks. I've updated the patch according to your comments: > > http://sourceforge.net/support/tracker.php?aid=1226187 > > This may go into 5.3.dev. Can you immediately spot any changes that do > *not* apply to 5.[12]? I've applied the patch to all of 5.[123].x. 5.1.x doesn't support "-3[kKmM]", so I left this single change (in snmpcmd.1.def) out, of course. While applying the patch I noticed that both 5.2.x and 5.1.x documentation doesn't really mention AES as a privProtocol, although 5.2.x supports AES|AES128 and 5.1.x supports AES128|AES192|AES256. Shouldn't we align 5.1.x to also accept "AES" (=AES128) and fully document "AES" (at various places) for 5.[12].x? +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/...et-snmp-coders |