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 3DA545388B for ; Tue, 19 Apr 2005 17:18:07 -0300 (ADT) 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 63703-09 for ; Tue, 19 Apr 2005 20:17:57 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.197.194]) by svr1.postgresql.org (Postfix) with SMTP id 041725362C for ; Tue, 19 Apr 2005 17:17:55 -0300 (ADT) Received: (qmail 18780 invoked by uid 500); 19 Apr 2005 20:37:27 -0000 Date: Tue, 19 Apr 2005 15:37:27 -0500 From: Bruno Wolff III To: Wim Bertels Cc: pgsql-admin@postgresql.org Subject: Re: brute force attacking the password Message-ID: <20050419203727.GA18200@wolff.to> Mail-Followup-To: Bruno Wolff III , Wim Bertels , pgsql-admin@postgresql.org References: <200504182027.j3IKRtV09046@candle.pha.pa.us> <42651CFF.1020703@khleuven.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42651CFF.1020703@khleuven.be> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.009 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/273 X-Sequence-Number: 17286 On Tue, Apr 19, 2005 at 17:00:15 +0200, Wim Bertels wrote: > >Can't people use PAM to get this effect if they want it? > > what if u use pam with ldap, then u can use pg brute force cracking to > obtain the ldap password, which is probably a bigger problem You don't have to use it with LDAP. It does provide some password controls, that should slow things down a little. However, you are going to have a tough time preventing password guessing without making denial of service attacks easy. > > >For most people password guessing isn't going to be a big problem as > >the database won't be accessible from totally untrusted places and watching > >the log files for guessing will probably be a good enough solution. > > what if u do want the database to be globally accessible.. Then you have a much more difficult situation. One option is to bind user names to specific allowed IP addresses.