MIME-Version: 1.0
References: <8574f8b4-7327-0c95-1199-214b78e0af7f@posteo.de>
In-Reply-To: <8574f8b4-7327-0c95-1199-214b78e0af7f@posteo.de>
From: Dave Page <dpage@pgadmin.org>
Date: Wed, 26 May 2021 13:46:05 +0100
Message-ID: 
 <CA+OCxowU7uPHBRt1RPZUXM-SS88YtRnScfri8P1DbnrvJ4OKmw@mail.gmail.com>
Subject: Re: Bug #6337
To: Florian Sabonchi <sabonchi@posteo.de>
Cc: pgadmin-hackers <pgadmin-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000004b39fb05c33b07b8"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BOCxowU7uPHBRt1RPZUXM-SS88YtRnScfri8P1DbnrvJ4OKmw%40mail.gmail.com>
Precedence: bulk

--0000000000004b39fb05c33b07b8
Content-Type: text/plain; charset="UTF-8"

Hi

On Wed, May 26, 2021 at 1:40 PM Florian Sabonchi <sabonchi@posteo.de> wrote:

> Hello,
>
> Is someone already working on ticket #6337 or can I start working on it?
>
> https://redmine.postgresql.org/issues/6337


Not as far as I know. Please feel free to work on it.

Do you have a design in mind? I would suggest maybe adding a
"login_attempts" column to the user table in the config database, and
having a parameter in config.py to define the maximum number of login
attempts allowed. login_attempts would be incremented for every failed
login, and set to zero for a successful one. If it's value is >= to the
maximum in the config, login would be denied. There would also need to be
changes to the user management dialogue to show the status for each user,
and reset them.

Thanks!

-- 
Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: https://www.enterprisedb.com

--0000000000004b39fb05c33b07b8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi</div><br><div class=3D"gmail_quote"><div dir=3D"lt=
r" class=3D"gmail_attr">On Wed, May 26, 2021 at 1:40 PM Florian Sabonchi &l=
t;<a href=3D"mailto:sabonchi@posteo.de">sabonchi@posteo.de</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,20=
4,204);padding-left:1ex">Hello,<br>
<br>
Is someone already working on ticket #6337 or can I start working on it?<br=
>
<br>
<a href=3D"https://redmine.postgresql.org/issues/6337" rel=3D"noreferrer" t=
arget=3D"_blank">https://redmine.postgresql.org/issues/6337</a></blockquote=
><div><br></div><div>Not as far as I know. Please feel free to work on it.<=
/div><div><br></div><div>Do you have a design in mind? I would suggest mayb=
e adding a &quot;login_attempts&quot; column to the user table in the confi=
g database, and having a parameter in config.py to define the maximum numbe=
r of login attempts allowed. login_attempts would be incremented for every =
failed login, and set to zero for a successful one. If it&#39;s value is &g=
t;=3D to the maximum in the config, login would be denied. There would also=
 need to be changes to the user management dialogue to show the status for =
each user, and reset them.</div><div><br></div><div>Thanks!</div><div>=C2=
=A0</div></div>-- <br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=
=3D"ltr">Dave Page<br>Blog: <a href=3D"https://pgsnake.blogspot.com" target=
=3D"_blank">https://pgsnake.blogspot.com</a><br>Twitter: @pgsnake<br><br>ED=
B: <a href=3D"https://www.enterprisedb.com" target=3D"_blank">https://www.e=
nterprisedb.com</a><br><br></div></div></div>

--0000000000004b39fb05c33b07b8--