>>Thanks for the link, it looks like this is what I'm looking for, but unfortunately when I test it the decrypted string is not the same as when I decrypt with FPW and Cipher.FLL, also using the same password. Is Cipher50 supposed to output the same result as Cipher.FLL? What then could be the reason that the output does not match?
>
>
>Hi Christian,
>
>Cipher50 will not produce the same encryption/decryption results as previous versions of Cipher.FLL. It's been a long time since I looked at that code. But I did a few things to shrink the DLL and make it faster. If you are migrating from earlier versions of Cipher, you'll probably have to create a small script to roll through your records and unencrypt with the earlier version and reencrypt with Cipher50.
>
>I would add that the Cipher50 encryption algorithm is very rudimentary and would be considered weak encryption compared to today's standards. It'll hide values from the average person snooping around. But won't stand up to a techie who is determined to find out the encrypted values.
>
>Hope this helps.
>
>Guy
Thanks for your comment, that clears up the problem that I'm having. Only that I cannot re-encrypt the passwords, because I cannot do any changes in the FPW code, because that would break a lot of other places.
The only workaround I was thinking about was to use FPW2.6 to do the decryption. Or perhaps better would be if I find somewhere the old Cipher.fll encryption algorithm and code it in VFP?
The password encryption strengh is not a big issue, because it's anyway open Foxpro tables.
Christian
Christian Isberner
Software Consultant