>Craig,
>
>Now that you're back amongst the living ...
>
>Would you mind telling what IV (initialization vector) you are using ?
>
>Any possibility to add a parameter to encrypt/decrypt that accepts an IV for CBC mode
>
>Thanks,

IV currently left as default (in the case of AES that's 32 byte array of nulls). As to the possibility of adding a parameter to specify the IV, yes. That was always the plan for modes CBC and CFB. Ideally I would allow devs to set IV and size then it could match .NET's (Rijndael/RijndaelManaged CreateDecryptor() for instance where the IV is 16 bytes i believe). I would also allow key length, block size, and block padding to be specified where applicable/allowed to vary. Also, could do something similar to .NET's PasswordDeriveBytes where a salt and key are fed to a hash to create an internal key actually used to encrypt the data. I'd like to provide as much compatibility with .NET and other platforms' implementations as possible so Visual FoxPro apps can freely produce/consume encrypted data from other sources. Not there yet, but someday.