Re: Storing encrypted data?

From: John Tregea <john(at)debraneys(dot)com>
To: Aaron Bono <postgresql(at)aranya(dot)com>
Cc: Michael Fuhr <mike(at)fuhr(dot)org>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Storing encrypted data?
Date: 2006-07-20 11:52:24
Message-ID: 44BF6E78.9090207@debraneys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Hi Aaron,

I removed them because when I bring the data back into my GUI, the
returns are treated as a record break by the software and I cannot
decrypt them or display the rest of the record that is not encrypted.

Regards

John T

Aaron Bono wrote:
> On 7/19/06, *John Tregea* <john(at)debraneys(dot)com
> <mailto:john(at)debraneys(dot)com>> wrote:
>
> 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.
>
>
>
> I usually leave the return characters where they are.
>
> I am curious, why did you decide to remove the return characters?
>
> ==================================================================
> Aaron Bono
> Aranya Software Technologies, Inc.
> http://www.aranya.com
> ==================================================================

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Kevin Nikiforuk 2006-07-20 13:46:41 Error when trying to use a FOR loop
Previous Message Florian Weimer 2006-07-20 07:31:16 Re: INSERT/UPDATEs cycles and lack of phantom locking