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 5A79B535D2 for ; Wed, 20 Apr 2005 12:01:28 -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 82070-10 for ; Wed, 20 Apr 2005 15:01:18 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.197.194]) by svr1.postgresql.org (Postfix) with SMTP id 593C35370F for ; Wed, 20 Apr 2005 12:01:13 -0300 (ADT) Received: (qmail 1115 invoked by uid 500); 20 Apr 2005 15:20:44 -0000 Date: Wed, 20 Apr 2005 10:20:44 -0500 From: Bruno Wolff III To: Wim Bertels Cc: pgsql-admin@postgresql.org Subject: Re: brute force attacking the password Message-ID: <20050420152044.GB512@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> <20050419203727.GA18200@wolff.to> <200504192254.41977.wim.bertels@khleuven.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200504192254.41977.wim.bertels@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/283 X-Sequence-Number: 17296 On Tue, Apr 19, 2005 at 22:54:32 +0200, Wim Bertels wrote: > > not an easy problem: it always seems to end up in DoS vs Brute Force Cracking. > So the only good and simple solution i can think of: use the best possible > password encrytion (or sufficient, a statistically zero chance when trying as > much connections -to brute force crack the password- as possible for a > significant amount of time.) Maybe you can use client side certificates. Those will be from a large enough space that guessing shouldn't be a problem. You should be able to make that work with PAM.