ASCrypt3 Rijndael Update
I made an update to Rijndael encryption in ASCrypt. There was a problem initializing the object if you were using a blocksize or key length other than the default.
It should be working better now. Of course, I still can't get it to produce the same results as ColdFusion's Encrypt function.
I did do some research into how CF's encrypt function is implemented. It uses FIPS-197. Read the Boringly long spec. In the FIPS implementation, the block size is constant at 128 bits.
Using the same key and source string (and Block Size), I would expect two different implementations of the same encryption algorithm to produce the same encrypted string. Most likely there is a bug with the ASCrypt implementation.
Last Saturday it was 60 degrees. Today we have a dusting of snow and flurries continuing to come down. I love New England.




Toku
MD5 and SHA1 encryption appears to produce similar results.
Base64 encoding works identically in both cases.
I could not get Rijndael (AKA AES) encryption to work. I've spent a lot of time on it without any luck. Based on my searching I couldn't get two AES encryption methods to return the same results.
I'd love some help if you want to take a look at the code.
Both MD5 and SHA1 are hash functions that can't be decrypted. So they are not what I am looking for.
http://tales-of-coldfusion.blogspot.com/
I don't see any posts there about AES and Flex + ColdFusion. Are you referring to this post?
http://tales-of-coldfusion.blogspot.com/2007/07/st...
That said, I have heard from people who used ASCrypt3 AES to pass data back and forth between Java and Flex.
I was able to get AES working between CF and Flex using a different encryption package. ( http://crypto.hurlant.com/ ).