From: Wim Bertels <wim.bertels@khleuven.be>
To: Bruno Wolff III <bruno@wolff.to>
Cc: pgsql-admin@postgresql.org
Subject: Re: brute force attacking the password
Date: Tue, 19 Apr 2005 22:54:32 +0200
Message-ID: <200504192254.41977.wim.bertels@khleuven.be> (raw)
In-Reply-To: <20050419203727.GA18200@wolff.to>
References: <200504182027.j3IKRtV09046@candle.pha.pa.us>
<42651CFF.1020703@khleuven.be>
<20050419203727.GA18200@wolff.to>
On Tuesday 19 April 2005 22:37, Bruno Wolff III seinde rooksignalen:
> On Tue, Apr 19, 2005 at 17:00:15 +0200,
>
> Wim Bertels <wim.bertels@khleuven.be> 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.
anayway, it makes sense to use ldap if one has several services over different
machines,..
>
> > >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.
not a option, due to user requirements
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.)
--
Wim Bertels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: wim.bertels@khleuven.be, bruno@wolff.to
Subject: Re: brute force attacking the password
In-Reply-To: <200504192254.41977.wim.bertels@khleuven.be>
References: <200504182027.j3IKRtV09046@candle.pha.pa.us> <42651CFF.1020703@khleuven.be> <20050419203727.GA18200@wolff.to> <200504192254.41977.wim.bertels@khleuven.be>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox