pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: viewing source code
Date: Thu, 20 Dec 2007 15:52:14 -0500
Message-ID: <20071220205214.GW4924@crankycanuck.ca> (raw)
In-Reply-To: <b42b73150712201235k7f41c4c7k92321af29ec768e5@mail.gmail.com>
References: <1A6E6D554222284AB25ABE3229A92762112A33@nrtexcus702.int.asurion.com>
	<476A9ADF.5030101@commandprompt.com>
	<90bce5730712201047m4dd0fe05k6b1fccc57897326f@mail.gmail.com>
	<20071220114011.64a650d7@commandprompt.com>
	<20071220200739.GC11586@alvh.no-ip.org>
	<b42b73150712201235k7f41c4c7k92321af29ec768e5@mail.gmail.com>

On Thu, Dec 20, 2007 at 03:35:42PM -0500, Merlin Moncure wrote:
> 
> Key management is an issue but easily solved.  Uber simple solution is
> to create a designated table holding the key(s) and use classic
> permissions to guard it.  

Any security expert worth the title would point and laugh at that
suggestion.  If the idea is that the contents have to be encrypted to
protect them, then it is just not acceptable to have the encryption keys
online.  That's the sort of "security" that inevitably causes programs to
get a reputation for ill-thought-out protections.

A




view thread (60+ messages)  latest in thread

Message-ID: <20071220205214.GW4924@crankycanuck.ca>
Permalink:  ../20071220205214.GW4924@crankycanuck.ca/
Also on:    postgresql.org/message-id/20071220205214.GW4924@crankycanuck.ca

 · 

reply
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-performance@postgresql.org
  Cc: ajs@crankycanuck.ca
  Subject: Re: viewing source code
  In-Reply-To: <20071220205214.GW4924@crankycanuck.ca>

* 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