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 65C3253736 for ; Thu, 14 Apr 2005 08:46:23 -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 15534-03 for ; Thu, 14 Apr 2005 11:46:22 +0000 (GMT) Received: from relay.khleuven.be (relay.khleuven.be [193.190.138.22]) by svr1.postgresql.org (Postfix) with ESMTP id D5C395372E for ; Thu, 14 Apr 2005 08:46:19 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by relay.khleuven.be (Postfix) with ESMTP id 33FFABC7F1 for ; Thu, 14 Apr 2005 13:46:19 +0200 (CEST) Received: from [10.2.10.238] (unknown [10.2.10.238]) by relay.khleuven.be (Postfix) with ESMTP id 3DFC6BC7DB for ; Thu, 14 Apr 2005 13:46:16 +0200 (CEST) Message-ID: <425E5807.2080205@khleuven.be> Date: Thu, 14 Apr 2005 13:46:15 +0200 From: Wim Bertels User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; nl-NL; rv:1.7.3) Gecko/20040910 X-Accept-Language: nl-be, nl, en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: brute force attacking the password Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200504/190 X-Sequence-Number: 17203 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 tnx,