Here is a little more information. Build the program and
encrypt on Win 2K. Execute the program on XP and
decryption fails.
Rebuild the program on XP, move the encrypted cipher data
from the Win 2K machine to the XP machine, and the data
decrypt correctly.
The reverse seems to be true as well, and also for Win
9x/ME systems. You have to build the application on the
system that is going to process the cipher data.
Evidently there is some system-dependent static linkage
involved with the Crpto 2.0 API.
Anybody know how to alleviate this problem? The data are
portable across Windows systems but the application
program, at least the crypto part of it, is not.
|