Re: Storing encrypted data?

Hi Aaron,

I found that your suggestion worked well. For some reason the IDE I use 
(Revolution) put a return character every 73rd character when it did the 
base64encode, but I strip those out and there no further problems. I 
don't even have to put them back later to decode it.

Thanks

John T

Aaron Bono wrote:
> On 7/17/06, *John Tregea* <john@debraneys.com 
> <mailto:john@debraneys.com>> wrote:
>
>     Hi Michael,
>
>     Thanks for your advice. I was looking at the bytea data type in the
>     PostgreSQL book I bought (Korry and Susan Douglas, second edition). I
>     was concerned that if I have to escape certain characters like the
>     single quote or the backslash, how do I guarantee that the escaped
>     version does not already appear in the encrypted string?
>
>     Should I use the octal value to escape the single quote (\047) and
>     backslash (\\134)?
>
>     Those character sequences are extremely unlikely to occur in an
>     encrypted string.
>
>     Is the the right approach ?
>
>     Also... I note that I cannot change the data type of my field from
>     text
>     to bytea (I am using PGADMIN III). Do you know why? 
>
>
>  
> When I have data like this, I do a Base64 encoding.  The string ends 
> up longer but I no longer have to worry about special characters 
> mucking things up.
>
> ==================================================================
>    Aaron Bono
>    Aranya Software Technologies, Inc.
>    http://www.aranya.com
> ==================================================================