From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-general@postgresql.org
Subject: Re: Encrypted column
Date: Tue, 5 Jun 2007 11:27:26 -0400
Message-ID: <20070605152726.GU4818@phlogiston.dyndns.org> (raw)
In-Reply-To: <466572F0.3070900@cox.net>
References: <46645B01.6070605@terra.com.br>
<4664983F.4010700@burntmail.com>
<46656398.1090203@cox.net>
<20070605135951.GB8140@alvh.no-ip.org>
<466572F0.3070900@cox.net>
On Tue, Jun 05, 2007 at 09:28:00AM -0500, Ron Johnson wrote:
>
> If he is a CC customer, the system (which I am DBA of) bills his
> card directly, saving the customer much time and effort.
So surely what you have is a completely separate system that has
exactly one interface to it, that is signaled to provide a
transaction number and that only ever returns such a transaction
number to the "online" system, and that is very tightly secured,
right?
It is possible to make trade-offs in an intelligent manner, for sure,
but you sure as heck don't want that kind of data stored online with
simple reversible encryption.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
The whole tendency of modern prose is away from concreteness.
--George Orwell
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: ajs@crankycanuck.ca, pgsql-general@postgresql.org
Subject: Re: Encrypted column
In-Reply-To: <20070605152726.GU4818@phlogiston.dyndns.org>
* 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