>> That article is completely useless.  Obviously you didn't read what i wrote in the previous paragraph

Please remember that everyone here is a volunteer and gives their time and knowledge freely to help others.

If you don't like the answers you get, then please feel free to go elsewhere for them but there's no call to be rude to someone who was only trying to help.

Hi,

I'm experiencing a problem with _crypt.vcx where decryption sometimes fails on certain computers but not others.  Has anyone run into this and developed a solution

Thanks,

Rob

Alex,

Thanks for the quick and informative reply.  I actually encrypted the data myself on WinXP Pro using FoxPro 8 and rsaenh.dll and the decryption fails also on some (not all) WinXP Pro computers that also use FoxPro 8 and rsaenh,dll (save version dll too).

One thing that may be relevant is the computers had Fox 7 installed and then Fox 8 upgrade, so both versions are resident.

Does that sound symtomatic of the same 40 vs 128 bit issue

Thanks!

Rob

I forgot to ask whether we can solve the problem by just ensuring all computers running the affected software have the same configuration - like the same version of some file(s).  Since they are all in-house computers our IT guys can control the config.

Thx,

Rob

Thanks - I'll try Craig's code.

Rob

I had a little time to read MSDN docs about RSA public / private key pair, encrypting, CAPICOM, Certificates, EnvelopedData, PFX files. The sample is vbscript based, but we know that to port it into VFP not a challenge.

Ok, let's see it. I have a PFX file, what was created by CIPHER. Just to have something. I used this passphrase while creating the certificate: "a very secret passphrase of the private key".

I can load it this way:
set oCert = Createobject("CAPICOM.Certificate")
oCert.Load "D:\test\test.pfx", "a very secret passphrase of the private key", CAPICOM_KEY_STORAGE_USER_PROTECTED, CAPICOM_CURRENT_USER_KEY

This certificate has a public key, private key. To use it, the EnvelopedData look like usable. It's really simple. Grab an EnvelopedData object, write something into the content property, add recipipents to it and finally call the encrypt method. The object automatically generates a symmetric key, what will be used to encrypt the large amount of content. This key will be encrypted by the public key of recipients. The default settings of the EnvelopedData obejct can be configured to strengthen the encryption or whatever you want. A sample:

set oEnvelope = createobject("CAPICOM.EnvelopedData")
oEnvelope.Algorithm.Name= CAPICOM_ENCRYPTION_ALGORITHM_AES
oEnvelope.Algorithm.KeyLength=CAPICOM_ENCRYPTION_KEY_LENGTH_MAXIMUM
oEnvelope.Content="Here's some very important and confidental data"
oEnvelope.Recipients.Add oCert
sSecret=oEnvelope.Encrypt(CAPICOM_ENCODE_BASE64)

The format of message what we got this way is PKCS #7. To decrypt the message is a joke. Just call the decrypt method of the EnvelopedData object with only one parameter, like this:

Set EnvelopedData = CreateObject("CAPICOM.EnvelopedData")
EnvelopedData.Decrypt sSecret
wscript.echo "Decrypted text is: " & EnvelopedData.Content

Okay. Decryption method searches for the private key in the "My" certificate store at current user or the local machine. There's no way to setup a file for decryption.

yeah u are rite ...

when u post your question dun expect forummers can solve 100 % your question.

We all here just share our knowledge and experience.