3DES from Java - CryptoAPI

Question

Hi All,
I'm facing a problem that is:
I encrypt data in Java client using 3DES algorithm("DESede/ECB/NoPadding" for the Cipher object and "DESede" for the SecretKey one). Our server is made on C# and it decrypts the data using .NET TripleDESCryptoServiceProvider class. No problem at all...
The problem appears when this encrypted data (by Java) is passed to C++ client (GINA) that uses CryptoAPI with CALG_3DES parameter for data decryption. The "key base" is exactly the same byte array of 24 elements that's used for Java SecretKey creation. But the result of CryptDecrypt() is 0x80090005 that means "Bad Data". I've tried this with thew most simple data (i.e. BYTE data[] = {1,2,3,4,5,6,7,8}).
What can be the problem ? The key or the Data or maybe some initialization parameter ( inspite of using deafult key parameters in CryptoAPI)???
Thanx a lot for any clue.
P.S. I've also tried to encrypt in Java with PKCS5Padding since
"The only padding method currently defined is
PKCS5_PADDING" appears in MS SDK.
But the result is the same....

Answer 1

1. Both sides use 3DES algorithm with CBC mode, the same IV and PKCS5 padding (DESede/CBC/PKCS5Padding).
2. At the java side the key is produced in the following manner:
DESedeKeySpec keyspec = new DESedeKeySpec(key);
SecretKeyFactory keyfactory = SecretKeyFactory.getInstance(keyAlg);
SecretKey secretKey = keyfactory.generateSecret(keyspec);where key is a byte array of 24 elements and keyAlg = "DESede".
3. At CryptoAPI side I use the same settings for the key and the algorithm but the key itself is not derived (as I've tried before) but is packed to PLAINTEXTKEYBLOB and then imported via CryptImportKey(). The key data that is inserted to this blob is exactly the same 24 bytes from the previous paragraph.
Good luck to all ! :-)