>
> Good Morning,
>
> Rijndael when it encrypts a string,, upon a particular combination of
> characters, will input an arbitrary hex 00 into the encrypted string, and
> when the string is passed by cold fusion with this hex 00, cold
> fusion will
> truncate the string at the hex 00 ( apparently seeing it as end of string)
> which in turns makes us lose a significant amount of data in the
> string. I
> have not been able to find any documentation on this and was wondering if
> anyone else had seen this behavior, and is there a setting to control it.
> We can fix the problem programmatically, but it will cause a
> lengthening of
> the data string that is passed to a database or file etc...
Normal behavior. C and C++ have traditionally used a NULL to indicate the
end of a text string. Since your encrypted text string is not _really_ a
simple text string anymore, you'll have to use something else designed to
handle binary data. Save the byte data in query structs, etc.
.... or maybe do an in-place encryption to base64. :)
--min
~~~~~~~~~~~~~ Paid Sponsorship ~~~~~~~~~~~~~
Get Your Own Dedicated Win2K Server! Instant Activation for $99/month w/Free Setup
from SoloServer PIII600 / 128 MB RAM / 20 GB HD / 24/7/365 Tech Support Visit
SoloServer, https://secure.irides.com/clientsetup.cfm.
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
