Clever Geek Handbook

Windows 2000 and Windows 2003 RC2 encryption / decryption using Windows Crypto API?

Our application encrypts a value using RC2 in C ++ code and I wrote a decryption procedure in .NET

The problem is that it works fine on our dev server which is Windows 2003 but does not work on Windows 2000. It works with the same code and I checked everything else and it seems there are differences in encryption method 2.

Anyone have any experience?

+1


source to share


3 answers


  • Make sure Windows 2000 has SP3, or encryption is much less likely to work, especially if you are using Capicom (or api it wraps).
  • Not all encryption algorithms and key lengths are supported in Windows 2000 when using Capicom (or api it wraps).


+1


source


There's an incomprehensible problem with win2000 / winxp encryption / decryption. The cryptographic service provider on win2000 has 40 for the effective key length and is the default even if you are using a 128 bit key. So to fix this, you have to manually reset to use the effective key length in 2000, or you can set it to 40 before decrypting on winxp (or win2003 in my case).



If you are using C # for decryption , you cannot set the effective key size to something other than the key size if you are using the RC2CryptoServiceProvider class.

0


source


I have the same problem between XP SP1 and XP SP2 using an encryption provider, the encrypted value is different for one specific cryptographic code which I cannot remember at the moment.

0


source






More articles:


All Articles