In general SNMPv3 uses two algorithm for privacy i.e. DES and AES. Currently we are using sharpSnmpLib version 1.0.1. It doesnt have support for AES so we just want to know your plan for the same.
Comments: Next time please open a discussion thread. The issue tracker is only for issues. From http://sharpsnmplib.codeplex.com/releases you can see we don't have a 1.0.1 release (we have 1.0 and 1.1 though). So can you confirm that you are using #SNMP? If you use another library in fact, we won't be able to help. Our AES support was first introduced in Sept 2009, https://github.com/lextm/sharpsnmplib/commits/master/SharpSnmpLib/Security/AESPrivacyProvider.cs So you must upgrade to Trident Refresh and above so as to utilize it. Please note that it is recommended to use our 7.5 release (BigDipper Refresh), or 7.6 (TritonMate M1). The long term plan is to soly support DES officially. The DES/AES support comes from http://snmpsharpnet.com, so if you want other privacy providers, you can write your own and utilize the source code of SNMP#NET, or any other encryption libraries.
Comments: Next time please open a discussion thread. The issue tracker is only for issues. From http://sharpsnmplib.codeplex.com/releases you can see we don't have a 1.0.1 release (we have 1.0 and 1.1 though). So can you confirm that you are using #SNMP? If you use another library in fact, we won't be able to help. Our AES support was first introduced in Sept 2009, https://github.com/lextm/sharpsnmplib/commits/master/SharpSnmpLib/Security/AESPrivacyProvider.cs So you must upgrade to Trident Refresh and above so as to utilize it. Please note that it is recommended to use our 7.5 release (BigDipper Refresh), or 7.6 (TritonMate M1). The long term plan is to soly support DES officially. The DES/AES support comes from http://snmpsharpnet.com, so if you want other privacy providers, you can write your own and utilize the source code of SNMP#NET, or any other encryption libraries.