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 0643E533B1 for ; Tue, 19 Apr 2005 10:13:17 -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 70372-09 for ; Tue, 19 Apr 2005 13:13:10 +0000 (GMT) Received: from relay.khleuven.be (relay.khleuven.be [193.190.138.22]) by svr1.postgresql.org (Postfix) with ESMTP id 7B3D8533C8 for ; Tue, 19 Apr 2005 10:13:06 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by relay.khleuven.be (Postfix) with ESMTP id 11038BC868; Tue, 19 Apr 2005 15:13:08 +0200 (CEST) Received: from [10.2.10.238] (unknown [10.2.10.238]) by relay.khleuven.be (Postfix) with ESMTP id 53055BC799; Tue, 19 Apr 2005 15:13:03 +0200 (CEST) Message-ID: <426503DA.8080609@khleuven.be> Date: Tue, 19 Apr 2005 15:12:58 +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: Bruce Momjian Cc: pgsql-admin@postgresql.org Subject: Re: brute force attacking the password References: <200504182027.j3IKRtV09046@candle.pha.pa.us> In-Reply-To: <200504182027.j3IKRtV09046@candle.pha.pa.us> 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/257 X-Sequence-Number: 17270 Bruce Momjian schreef: >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? > > evident remarks: http://www.woodmann.com/fravia/protec.htm SHS instead of MD5? http://www.secinf.net/firewalls_and_VPN/Firewalls_Complete/Firewalls_Complete__Cryptography_Is_it_Enough.html ..