pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: BUG #16522: No anti-violent cracking mechanism
2+ messages / 1 participants
[nested] [flat]
* Re: BUG #16522: No anti-violent cracking mechanism
@ 2020-07-01 10:54 Magnus Hagander <magnus@hagander.net>
0 siblings, 0 replies; 2+ messages in thread
From: Magnus Hagander @ 2020-07-01 10:54 UTC (permalink / raw)
To: abcxiaod@126.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
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/;
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/;
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2020-07-01 10:54 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-07-01 10:54 Re: BUG #16522: No anti-violent cracking mechanism Magnus Hagander <magnus@hagander.net>
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