pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Brian A. Seklecki <lavalamp@spiritual-machines.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: PKI/SSL Client/Server Certificate Authentication
Date: Fri, 13 Jan 2006 12:19:38 -0500 (EST)
Message-ID: <20060113114049.D38232@arbitor.digitalfreaks.org> (raw)
In-Reply-To: <25602.1137168524@sss.pgh.pa.us>
References: <20060113095615.S38232@arbitor.digitalfreaks.org>
	<25602.1137168524@sss.pgh.pa.us>

On Fri, 13 Jan 2006, Tom Lane wrote:

> "Brian A. Seklecki" <lavalamp@spiritual-machines.org> writes:
>> If a "bad person" were to somehow obtain a copy of the source code with a
>> password embedded in the connect string (Steal it from a developer who
>> uses Windows, or maybe convince Apache to not interpret PHP before sending
>> to the client, something stupid like that), they would still be unable to
>> connect without a client certificate.
>
> So they steal the client certificate file instead of (the file
> containing) the password.  How exactly is this more secure?

You'd have to get a local shell on the server *plus* the password.

If a hacker can get a local shell on your web server (not a multi-user 
environment, obviously), and the Web server isn't in a jail, then they've 
probably got your database server too, and you might as well pack up and 
head home.

But with OCSP, the CA for the organization can revoke the validity of a 
Cert at any time by updating the CRL.

The password is entirely optional for the user.  When you've got a Vhost 
running multiple Apps talking to the same BD, and the Web servers runs as 
the "www" or "http" user, you can even plug multiple database user 
passwords into user ~/www/.pgpass and the username is mapped via the 
Client X.509 cert.

In short, it's a deterrent to hackers and a convenience to admins.  But we 
all know if someone wants in, they'll get in and it won't be some kind of 
attack a weakness in X.509 PKI, it will be the develpoer on Windows that 
opens the e-mail with the attachment (or image file!)

~BAS

>
> 			regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

l8*
 	-lava

x.25 - minix - bitnet - plan9 - 110 bps - ASR 33 - base8



view thread (4+ messages)  latest in thread

Message-ID: <20060113114049.D38232@arbitor.digitalfreaks.org>
Permalink:  ../20060113114049.D38232@arbitor.digitalfreaks.org/
Also on:    postgresql.org/message-id/20060113114049.D38232@arbitor.digitalfreaks.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: lavalamp@spiritual-machines.org, tgl@sss.pgh.pa.us
  Subject: Re: PKI/SSL Client/Server Certificate Authentication
  In-Reply-To: <20060113114049.D38232@arbitor.digitalfreaks.org>
  References: <20060113095615.S38232@arbitor.digitalfreaks.org> <25602.1137168524@sss.pgh.pa.us> <20060113114049.D38232@arbitor.digitalfreaks.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