BUG #16522: No anti-violent cracking mechanism

Started by PG Bug reporting formalmost 6 years ago2 messagesbugs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following bug has been logged on the website:

Bug reference: 16522
Logged by: yi Ding
Email address: abcxiaod@126.com
PostgreSQL version: 10.13
Operating system: linux
Description:

Pg database is not locked after password verification fails several times.

#2Magnus Hagander
magnus@hagander.net
In reply to: PG Bug reporting form (#1)
Re: BUG #16522: No anti-violent cracking mechanism

On Wed, Jul 1, 2020 at 12:07 PM PG Bug reporting form <
noreply@postgresql.org> wrote:

The following bug has been logged on the website:

Bug reference: 16522
Logged by: yi Ding
Email address: abcxiaod@126.com
PostgreSQL version: 10.13
Operating system: linux
Description:

Pg database is not locked after password verification fails several times.

Correct, there is no such feature built-in, so there is no bug in something
that does not work.

If you want this feature you can integrate PostgreSQL with numerous
external authentication methods such as gssapi, ldap, radius or pam, all of
which can provide such functionality if set up right. You can also use
fail2ban or some simple log-tailing script that implements it.

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/&gt;
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/&gt;