Re: password with Rijndael Encryption

[Bill McCormick]

Its not that simple. See the posting from David Shambroom above. He is 
the lead designer on the new Cache security. He is stating it is not the 
algorithm at issue here. It is that we implemented a different cipher 
system for AES encoding then the one .Net has implemented. I suspect 
this is not simply the case of adding the vector but he would be the 
person to know.

Denver Braughler wrote:
Bill McCormick wrote:
We won't give out our source.
Do you verify that it is FIPS Pub 140-2 compliant?
Anyway, is making the vector the third (and optional) call-in argument an enhancement 
that ISC is likely to entertain?  Or is that totally buried in the code?
If the code isn't COS, that makes it all the more desirable to use on the presumption that it is optimized compiled or assembled code.