Re: BUG #16522: No anti-violent cracking mechanism

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: BUG #16522: No anti-violent cracking mechanism
Дата
Msg-id CABUevEzYSK-f=53rH91ZyGuduvLnfLzOXdWM2sj3A8tTCLLzeQ@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #16522: No anti-violent cracking mechanism  (PG Bug reporting form <noreply@postgresql.org>)
Список pgsql-bugs
Дерево обсуждения


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.

--

В списке pgsql-bugs по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #16522: No anti-violent cracking mechanism
Следующее
От: Dmitry Dolgov
Дата:
Сообщение: Re: BUG #16500: SQL Abend. select multi_key_columns_range_partition_table