What DLL is in use in _crypt.vcx ?

[Goofus828]

We have 1 client that cannot get passed our password/decrypt routine. The other 40 clients can.

This client is using our VFP9 software on a virtual machine( win 7 ).

We are using the FFC\_crypt.vcx class that was loaded with VFP9.

Here is a snippet of that code in the _crypt class.

Declare INTEGER CryptDeriveKey ;
	IN WIN32API AS CryptDeriveKey ;
	INTEGER hProviderHandle, ;
	INTEGER nALG_ID, ;
	INTEGER hBaseDataHandle, ;
	INTEGER nFlags, ;
	INTEGER @hCryptKeyHandle

I would like to know where the WIN32API file is, or is it embedded in another DLL such as Kernal32.dll or gdi32.dll etc, etc.

I will use this information to determine if the virtual machine is missing something.

Thanks.

 

[Olaf Doschke]

WIN32API is a keyword for a whole bunch of system core DLLs, see the help file:

If you specify WIN32API for the LibraryName, Visual FoxPro searches for the 32-bit Windows .dll function in Kernel32.dll, Gdi32.dll, User32.dll, Mpr.dll, and Advapi32.dll.

Searching the MSDN you find this function is part of the Advapi32.dll

Known problems with encryption are export restrictions on cryptography providers, and the irony is we have a problem with defaults due to the relaxing of US export restrictions. Microsoft changed the default RSA algorithm from 40Bits to 128Bits. This way, unless you take action, an encryption done in one OS (say WinXP) does not decrypt properly in another OS (eg Windows 2000).

http://fox.wikis.com/wc.dll?Wiki~CryptoAPI

Bye, Olaf.

 

[DSummZZZ]

I have better results using Craig Boyd's encryption stuff:

http://www.sweetpotatosoftware.com/SPSBlog/2009/08/09/MajorVFPEncryptionUpdate.aspx

-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm