X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 3F77AD1DAA0 for ; Sun, 15 Feb 2004 05:26:59 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 17776-08 for ; Sun, 15 Feb 2004 01:27:01 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id DA9FAD1D8AE for ; Sun, 15 Feb 2004 01:26:54 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1F5QxfT005587; Sun, 15 Feb 2004 00:26:59 -0500 (EST) To: hehe88hk@yahoo.com.hk (Eric) Cc: pgsql-admin@postgresql.org Subject: Re: forcing SSL In-reply-to: References: Comments: In-reply-to hehe88hk@yahoo.com.hk (Eric) message dated "14 Feb 2004 11:13:05 -0800" Date: Sun, 15 Feb 2004 00:26:59 -0500 Message-ID: <5586.1076822819@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/218 X-Sequence-Number: 12392 hehe88hk@yahoo.com.hk (Eric) writes: > In order to ensure all user are making SSL connection to the database, > in the file pg_hba.conf, I change all the first columns into "hostssl" > such that there is neither "host" nor "local" left. > However, when I try to use a program written in Tcl to access the > database, even without the option "requiressl=1" for "pg_connect", the > program can still make connection to the database. Is this a local-Unix-socket connection? We don't bother with SSL on such connections. There's no point --- the only way to eavesdrop on a local connection is to have broken into your kernel, at which point it's game over anyway. regards, tom lane PS: it also occurs to me you might have forgotten to SIGHUP the postmaster after editing pg_hba.conf...