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 5E92B53518 for ; Mon, 18 Apr 2005 17:28:47 -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 73512-07 for ; Mon, 18 Apr 2005 20:28:39 +0000 (GMT) Received: from candle.pha.pa.us (candle.pha.pa.us [64.139.89.126]) by svr1.postgresql.org (Postfix) with ESMTP id DEFD253462 for ; Mon, 18 Apr 2005 17:28:01 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id j3IKRtV09046; Mon, 18 Apr 2005 16:27:55 -0400 (EDT) From: Bruce Momjian Message-Id: <200504182027.j3IKRtV09046@candle.pha.pa.us> Subject: Re: brute force attacking the password In-Reply-To: <425E5807.2080205@khleuven.be> To: Wim Bertels Date: Mon, 18 Apr 2005 16:27:55 -0400 (EDT) Cc: pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.01 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/237 X-Sequence-Number: 17250 Wim Bertels wrote: > LS, > > is there a way of securing the postgresql-server against brute force > password cracking ? > iow: is there a way of setting eg a maximum number of login attempts, or > using a time-out or ..? > > + securing on server level No, there is not. Does anyone want to suggest a possible implementation for the TODO list? -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073