From: Craig James <craig_james@emolecules.com>
To: Kris Deugau <kdeugau@vianet.ca>
To: pgsql-admin@postgresql.org
Subject: Re: secret key for encryption
Date: Fri, 16 Jul 2010 10:26:35 -0700
Message-ID: <4C40964B.4050606@emolecules.com> (raw)
In-Reply-To: <4C409372.6060102@vianet.ca>
References: <4C4038AC0200002500033716@gw.wicourts.gov>
<4C4038EC0200002500033719@gw.wicourts.gov>
<4C4038EC0200002500033719@gw.wicourts.gov>
<4C408F49.10605@emolecules.com>
<4C409372.6060102@vianet.ca>
Kris,
[Replying to list, too.]
On 7/16/10 10:14 AM, Kris Deugau wrote:
> Craig James wrote:
>> This isn't exactly a Postgres question, but I hope someone in the
>> community has solved it.
>>
>> I want to encrypt some data in Postgres that arrives from Apache. How
>> do you store an encryption key in such a way that Apache CGIs can get
>> it, but a hacker or rogue employee who manages to access the machine
>> can't find out the encryption key?
>
> Short answer: You don't.
>
> Longer answer: You can tie things up with public-key encryption so that
> a different system can retrieve the data, but the system that put it in
> can't because it only has the public (encryption) key, not the private
> (decryption) key.
>
> Even that isn't safe from a rogue employee - what if that rogue is your
> seniour sysadmin with full root access on all your systems?
If we assume no escalation of priviliges, that is, Apache stays apache and users can't escalate to root, what then?
This must be a solved problem. Credit-card numbers are required to be encrypted by law. It wouldn't make sense for them to be encrypted but then find that the password is sitting around where anyone can find it. There must be any number of Postgres users who store encrypted credit card numbers and other personal data. How do they solve this problem?
Craig
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-admin@postgresql.org
Cc: craig_james@emolecules.com, kdeugau@vianet.ca
Subject: Re: secret key for encryption
In-Reply-To: <4C40964B.4050606@emolecules.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