From: Aaron Bono <postgresql@aranya.com>
To: John Tregea <john@debraneys.com>
Cc: Michael Fuhr <mike@fuhr.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: Storing encrypted data?
Date: Wed, 19 Jul 2006 09:34:25 -0500
Message-ID: <bf05e51c0607190734u691a2f13hc42f7d8325a45ff1@mail.gmail.com> (raw)
In-Reply-To: <44BDF054.5060603@debraneys.com>
References: <A70AE049E81A6A40879D5DC0AC8C38C9069508ED@venus.infics.com>
<44BAE3B0.8060403@debraneys.com>
<20060717030705.GA87022@winnie.fuhr.org>
<44BB28AC.3070302@debraneys.com>
<bf05e51c0607170855i632fdd2fob1455fdc8ef4c9d4@mail.gmail.com>
<44BDF054.5060603@debraneys.com>
On 7/19/06, John Tregea <john@debraneys.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
==================================================================
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: postgresql@aranya.com, john@debraneys.com, mike@fuhr.org
Subject: Re: Storing encrypted data?
In-Reply-To: <bf05e51c0607190734u691a2f13hc42f7d8325a45ff1@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox