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 C96EB9DCAC0 for ; Tue, 6 Dec 2005 13:38:04 -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 49270-07 for ; Tue, 6 Dec 2005 13:38:03 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from wolff.to (wolff.to [66.93.197.194]) by postgresql.org (Postfix) with SMTP id 7CA5B9DCAAF for ; Tue, 6 Dec 2005 13:38:02 -0400 (AST) Received: (qmail 28248 invoked by uid 500); 6 Dec 2005 17:42:28 -0000 Date: Tue, 6 Dec 2005 11:42:28 -0600 From: Bruno Wolff III To: Colton A Smith Cc: pgsql-admin@postgresql.org Subject: Re: ssl and/or md5 encryption Message-ID: <20051206174228.GA21130@wolff.to> Mail-Followup-To: Bruno Wolff III , Colton A Smith , pgsql-admin@postgresql.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.02 required=5 tests=[AWL=0.020] X-Spam-Score: 0.02 X-Spam-Level: X-Archive-Number: 200512/36 X-Sequence-Number: 19756 On Wed, Nov 30, 2005 at 08:24:34 -0500, Colton A Smith wrote: > > I specify md5 encryption in my pg_hba.conf file. Would using SSL on > top of this be overkill? md5 password hashing doesn't buy a whole lot. If packet sniffing is a significant threat for you, you probably want to consider forcing clients to use ssl. If you have cpu cycles to burn, you probably also want to use it.