I have checked the PKCS #12 paper.. there is only one password and salt padding defined, so I presume, Crypto++ and BC are doing this the same way.
The difference is pretty elementar and is related to the values of the ID byte (as defined in PKCS#12). BC defines different routines for the defined values of ID ID = 1 -> to derive an encrypt/decryption key ID = 2 -> to derive an IV for encrypt/decryption ID = 3 -> to derive an integrity check MAC Both mentioned ways to derive a key use ID=1 as fix value. Crypto++ does take the ID as parameter "purpose" in "DeriveKey", which can be set to any Byte value. So you only have to use the correct purpose value in Crypto++, to be compatible with BC (and PKCS#12 paper). Best regards MANO PS: We've been working on this problem together with Metalpalo. Thank you, Metalpalo. -- View this message in context: http://www.nabble.com/Different-secret-keys-with-192-and-256-length-tf4941415.html#a14167436 Sent from the Crypto++ Users mailing list archive at Nabble.com. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
