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 CD7E0D1EF2E for ; Fri, 19 Mar 2004 23:25:12 +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 47606-03 for ; Fri, 19 Mar 2004 19:25:13 -0400 (AST) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id 7E02BD1EF32 for ; Fri, 19 Mar 2004 19:25:08 -0400 (AST) Received: from out005.verizon.net (out005pub.verizon.net [206.46.170.143]) by www.postgresql.com (Postfix) with SMTP id C597FCF508B for ; Fri, 19 Mar 2004 19:25:06 -0400 (AST) Received: from spacemonkeylabs.com ([68.161.147.162]) by out005.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040319201417.QSFQ2677.out005.verizon.net@spacemonkeylabs.com> for ; Fri, 19 Mar 2004 14:14:17 -0600 Message-ID: <405B549B.9000607@spacemonkeylabs.com> Date: Fri, 19 Mar 2004 15:14:19 -0500 From: Mitch Pirtle Organization: Spacemonkey Laboratories User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'pgsql-admin@postgresql.org'" Subject: Re: Dynamic IP authentication References: <4F44C51ED1C9D311B761009027DC72181889CEE6@exch1.unh.edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from [68.161.147.162] at Fri, 19 Mar 2004 14:14:17 -0600 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/268 X-Sequence-Number: 12837 Sam Barnett-Cormack wrote: > On Fri, 19 Mar 2004, Richard Dockery wrote: > > >> Does anyone know a way of authenticating client applications with dynamic IP >> addresses? All our client machines are receiving dynamic IP addresses. Is >> there a way to set up the pg_hba file to allow for this, or is there another >> way to configure connections so as not to use this file? >> Any thoughts would be appreciated. >> Thank you! > > > > Open access to the whole IP range, but require passwords. I think you > can wrap in SSL as well. > This is what I do, and now I won't let non-SSL connections through. The pg_hba.conf entry that lets me connect over SSL from anywhere looks like this: hostssl all mitchy 0.0.0.0 0.0.0.0 password Of course you need to configure your database box with an SSL key, which is well documented. -- Mitch