X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D6AC58B9D5F for ; Tue, 22 Feb 2005 11:56:52 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 30528-10 for ; Tue, 22 Feb 2005 11:56:41 +0000 (GMT) Received: from 9.hellooperator.net (cpc3-cdif2-3-0-cust202.cdif.cable.ntl.com [81.103.32.202]) by svr1.postgresql.org (Postfix) with ESMTP id E16558B9B19 for ; Tue, 22 Feb 2005 11:56:42 +0000 (GMT) Received: from [10.4.0.5] (helo=eris.tenfour) by 9.hellooperator.net with esmtp (Exim 4.43) id 1D3Yef-0003UT-IQ for pgsql-admin@postgresql.org; Tue, 22 Feb 2005 11:56:42 +0000 Received: from rasputnik by eris.tenfour with local (Exim 4.44 (FreeBSD)) id 1D3Yef-0009V9-ET for pgsql-admin@postgresql.org; Tue, 22 Feb 2005 11:56:41 +0000 Date: Tue, 22 Feb 2005 11:56:41 +0000 From: Dick Davies To: PostgreSQL Admin Subject: pg_hba.conf Message-ID: <20050222115641.GR66519@eris.tenfour> Reply-To: Dick Davies Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.503 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: * X-Archive-Number: 200502/211 X-Sequence-Number: 16379 Just needed clarification on how pg_hba.conf operates. Does a specific host take precedence over a more general network setting? The local socket is only accessible to a certain group, but I don't want the overhead of SSL for loopback connections. If I connect to the server from the local machine, the connections show up as (eg) 10.2.3.4, the NIC ip. I was hoping the more specific 'host' entry would take entry over the universal 'hostssl' entry, but it does'nt seem to... I have this: root@eris:postgresql80-server$ cat /opt/pgsql/data/pg_hba.conf # TYPE DATABASE USER IP-ADDRESS METHOD local all all trust host all all 10.2.3.4/32 md5 hostssl all all 0.0.0.0/0 md5 Is there a way to say 'all IP traffic should be encrypted except one IP' that I'm missing? I know I could just add the local process into the dba group, but the app doesn't reconnect if the socket goes away on a db restart, so that's not ideal... -- 'That question was less stupid; though you asked it in a profoundly stupid way.' -- Prof. Farnsworth Rasputin :: Jack of All Trades - Master of Nuns