>>>>> "TA" == Thomas Anders <[EMAIL PROTECTED]> writes:
TA> This may well be one of a few exceptions. I do see code for support of TA> AES192 and AES256 in 5.1.x, but not in 5.2.x and later. I vaguely TA> remember them being dropped because of being non-standard. I have no TA> idea whether the corresponding code in 5.1.x ever worked. TA> Wes, can you please clarify on this? AES192 and AES256 were never fully supported. At one point in the past the AES IETF document was going to standardize the 192 and 256 modes, but ended up dropping it before the final release of the RFC. >From the net-snmp point of view we started supporting AES192 and 256 when the initial drafts started circulating. HOWEVER, we never supported it completely. You could not use passwords or master keys to get to the localized key because the hash algorithms (MD5 and SHA) didn't produce long enough keys and we never implemented the hash iterations required to producing the longer keys. In summary, you really shouldn't be using 192 and 256 anyway because it's not a standard and no one else does, and it was dropped for recent net-snmp versions anyway. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
