From: Bruno Wolff III <bruno@wolff.to>
To: Wim Bertels <wim.bertels@khleuven.be>
Cc: pgsql-admin@postgresql.org
Subject: Re: brute force attacking the password
Date: Wed, 20 Apr 2005 10:20:44 -0500
Message-ID: <20050420152044.GB512@wolff.to> (raw)
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>
On Tue, Apr 19, 2005 at 22:54:32 +0200,
Wim Bertels <wim.bertels@khleuven.be> 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.
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: bruno@wolff.to, wim.bertels@khleuven.be
Subject: Re: brute force attacking the password
In-Reply-To: <20050420152044.GB512@wolff.to>
References: <200504182027.j3IKRtV09046@candle.pha.pa.us> <42651CFF.1020703@khleuven.be> <20050419203727.GA18200@wolff.to> <200504192254.41977.wim.bertels@khleuven.be> <20050420152044.GB512@wolff.to>
* 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