From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brian A. Seklecki <lavalamp@spiritual-machines.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: PKI/SSL Client/Server Certificate Authentication
Date: Fri, 13 Jan 2006 11:08:44 -0500
Message-ID: <25602.1137168524@sss.pgh.pa.us> (raw)
In-Reply-To: <20060113095615.S38232@arbitor.digitalfreaks.org>
References: <20060113095615.S38232@arbitor.digitalfreaks.org>
"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?
regards, tom lane
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: tgl@sss.pgh.pa.us, lavalamp@spiritual-machines.org
Subject: Re: PKI/SSL Client/Server Certificate Authentication
In-Reply-To: <25602.1137168524@sss.pgh.pa.us>
References: <20060113095615.S38232@arbitor.digitalfreaks.org> <25602.1137168524@sss.pgh.pa.us>
* 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