pg.ddx.io pgsql-hackers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Michael Banck <mbanck@gmx.net>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>
Cc: Abhijit Menon-Sen <ams@toroid.org>
Cc: pgsql-hackers@lists.postgresql.org, 成之焕 <zhcheng@ceresdata.com>
Subject: Re: [PATCH] Exponential backoff for auth_delay
Date: Sun, 7 Apr 2024 09:43:39 +0200
Message-ID: <66124eab.500a0220.47342.091b@mx.google.com> (raw)
In-Reply-To: <F043D4E9-C115-4FA1-8A86-05351BE94214@yesql.se>
References: <65e62440.170a0220.f6a7c.6f7f@mx.google.com>
<20240305215044.GA3538518@nathanxps13>
<CAOYmi+=47C8PEXZ8C9xxTRPtTevJgioQxJ3_vvd45rAQXPBy-Q@mail.gmail.com>
<20240306161045.GA3542434@nathanxps13>
<CAOYmi+koiMd58P=k_S7wsLw17chw5g2Y8kc6MHzoOqOOZ9KXdA@mail.gmail.com>
<c7873369-4c91-4d03-b344-c21085da3122@enterprisedb.com>
<65e8f208.170a0220.ba91f.1ea3@mx.google.com>
<CAOYmi+k2jkTPeWxCvSi7qzAGLsckQyAyiuZcNjosNJpOBjjo2g@mail.gmail.com>
<CAOYmi+nkZ+BbmsbdXZEaULrv+fqL9gx1uyEBOKKNS8zYCy65dA@mail.gmail.com>
<F043D4E9-C115-4FA1-8A86-05351BE94214@yesql.se>
Hi,
On Wed, Mar 20, 2024 at 11:22:12PM +0100, Daniel Gustafsson wrote:
> > On 20 Mar 2024, at 22:21, Jacob Champion <jacob.champion@enterprisedb.com> wrote:
> >
> > On Wed, Mar 20, 2024 at 2:15 PM Jacob Champion
> > <jacob.champion@enterprisedb.com> wrote:
> >> I think solutions for case 1 and case 2 are necessarily at odds under
> >> the current design, if auth_delay relies on slot exhaustion to do its
> >> work effectively. Weakening that on purpose doesn't make much sense to
> >> me; if a DBA is uncomfortable with the DoS implications then I'd argue
> >> they need a different solution. (Which we could theoretically
> >> implement, but it's not my intention to sign you up for that. :D )
> >
> > The thread got quiet, and I'm nervous that I squashed it unintentionally. :/
> >
> > Is there consensus on whether the backoff is useful, even without the
> > host tracking? (Or, alternatively, is the host tracking helpful in a
> > way I'm not seeing?) Failing those, is there a way forward that could
> > make it useful in the future?
>
> I actually wrote more or less the same patch with rudimentary attacker
> fingerprinting, and after some off-list discussion decided to abandon it for
> the reasons discussed in this thread. It's unlikely to protect against the
> attackers we wan't to protect the cluster against since they won't wait for the
> delay anyways.
I have marked the patch "Returned with Feedback" now. Maybe I will get
back to this for v18, but it was clearly not ready for v17.
Michael
view thread (22+ messages)
Message-ID: <66124eab.500a0220.47342.091b@mx.google.com> Permalink: ../66124eab.500a0220.47342.091b@mx.google.com/ Also on: postgresql.org/message-id/66124eab.500a0220.47342.091b@mx.google.com ·
reply
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 using the --to and --cc options: reply via email To: pgsql-hackers@postgresql.org Cc: mbanck@gmx.net, daniel@yesql.se, jacob.champion@enterprisedb.com, tomas.vondra@enterprisedb.com, nathandbossart@gmail.com, ams@toroid.org, zhcheng@ceresdata.com Subject: Re: [PATCH] Exponential backoff for auth_delay In-Reply-To: <66124eab.500a0220.47342.091b@mx.google.com> * 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