X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id BE8569DC82E for ; Fri, 13 Jan 2006 12:08:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 33058-10 for ; Fri, 13 Jan 2006 12:08:48 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2A1959DCDC1 for ; Fri, 13 Jan 2006 12:08:46 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0DG8i7F025603; Fri, 13 Jan 2006 11:08:44 -0500 (EST) To: "Brian A. Seklecki" cc: pgsql-admin@postgresql.org Subject: Re: PKI/SSL Client/Server Certificate Authentication In-reply-to: <20060113095615.S38232@arbitor.digitalfreaks.org> References: <20060113095615.S38232@arbitor.digitalfreaks.org> Comments: In-reply-to "Brian A. Seklecki" message dated "Fri, 13 Jan 2006 10:23:23 -0500" Date: Fri, 13 Jan 2006 11:08:44 -0500 Message-ID: <25602.1137168524@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.087 required=5 tests=[AWL=0.087] X-Spam-Score: 0.087 X-Spam-Level: X-Archive-Number: 200601/161 X-Sequence-Number: 20249 "Brian A. Seklecki" 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