From: Ron Johnson <ron.l.johnson@cox.net>
To: pgsql-general@postgresql.org
Subject: Re: Encrypted column
Date: Tue, 05 Jun 2007 09:28:00 -0500
Message-ID: <466572F0.3070900@cox.net> (raw)
In-Reply-To: <20070605135951.GB8140@alvh.no-ip.org>
References: <46645B01.6070605@terra.com.br>
<4664983F.4010700@burntmail.com>
<46656398.1090203@cox.net>
<20070605135951.GB8140@alvh.no-ip.org>
On 06/05/07 08:59, Alvaro Herrera wrote:
> Ron Johnson wrote:
>> On 06/04/07 17:54, Guy Rouillier wrote:
>
>>> Many people consider two-way encryption to be insecure; two-way
>>> encryption means you can decrypt a value if you know the key, and it is
>>> insecure because you usually have to put the key into the source code.
>>> That means at least one person in your company, the programmer
>>> maintaining the source code, can learn all of your users' passwords.
>> Two-way encryption is needed for companies that store customer
>> credit cards.
>
> I thought that the advice for companies storing customer CCs was: don't.
Sometimes you "must".
An example from my industry: transponder "toll tags" and toll roads.
The customer pre-pays a certain amount based on expected usage,
and every time he drives thru a plaza, his balance decreases. Once
it drops to a certain threshold, more money needs to be added to the
account.
If he is a CASH/CHEK customer, a light at the lane flashes yellow
and (depending on the Agency) a message pops up saying, "Balance
low", so he drives over to the customer service center, stands in
line and pays his cash.
If he is a CC customer, the system (which I am DBA of) bills his
card directly, saving the customer much time and effort.
--
Ron Johnson, Jr.
Jefferson LA USA
Give a man a fish, and he eats for a day.
Hit him with a fish, and he goes away for good!
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: ron.l.johnson@cox.net, pgsql-general@postgresql.org
Subject: Re: Encrypted column
In-Reply-To: <466572F0.3070900@cox.net>
* 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