Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mcol5-0002mh-SU for pgsql-novice@arkaria.postgresql.org; Tue, 19 Oct 2021 13:02:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mcol4-0001ei-QE for pgsql-novice@arkaria.postgresql.org; Tue, 19 Oct 2021 13:02:22 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mcol4-0001eX-IG for pgsql-novice@lists.postgresql.org; Tue, 19 Oct 2021 13:02:22 +0000 Received: from mail-ed1-x531.google.com ([2a00:1450:4864:20::531]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mcol1-0007ok-Jt for pgsql-novice@lists.postgresql.org; Tue, 19 Oct 2021 13:02:21 +0000 Received: by mail-ed1-x531.google.com with SMTP id w19so12559467edd.2 for ; Tue, 19 Oct 2021 06:02:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IH3RysGKMn7+Kjpxxe/tM2FMQsaxxQkOmKHgl311Kr0=; b=cK1pM3PY5RgIlT06HrLmqQoPVF/6zNDVdWqLLnATwVnoktuGXns+qomdWGweImwGDp ueNJCAnNDJH3OH7OUtnzrsXwbrDrTPW29xGrGqbnznDAH3U1Vs54DiIoJzRv26E8uMxa SnQmuERix3ebUpZZgpUahwW3xFu/XVQJoD+H5Rd9TNrIZrzEPdceBLM2O9mKhPhRhf+s 8VjCUt5iCW6ZIs0LI35YGHoL15RN7XBkXOX554rIInPktNTJuwgWmxvyHcydI7jibKQx iPhRAWuoVyNcgHeWKrKSt6RGWDd/PlLchtXpDUCQFLoRSKgGY93xFZ3nHS2QkSnz2bXo pkPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IH3RysGKMn7+Kjpxxe/tM2FMQsaxxQkOmKHgl311Kr0=; b=YBK4TGd03Tz6/XLzZomhS37P52J9hlQOrFNsjH9qyaCXmt3oe9UR0uZjUkTx+t/yKi A/wPa/Hb0aub88ranis0c5iLLxKTc/zclpaDh6PHMoe4cpHsrfbJMMEvL+kmSspvUA8T IQ+IxpYkSEHjBDlPyR4LGy3Hg4/vvsZkPiYcbSEbfs5D/5ummRC3MxQGbbnjJCPM7fob zj+H0QSjIj0cqtF3YwqMknbYx+ki/Rjdfj0RFyKATFUyLcRLnqHBiNN6qNq2rSokyoZR GdNg8fnuWT9ewssmbNumd0EtNMsCn21dQFWZKNh+B7diVzgALJv4g38PVr6osvVJI7cC Uf6g== X-Gm-Message-State: AOAM533GvoC7tYTERBuViWpSOeYoVbrytgBslFYhutq8zmKV8ONPXF8D duWU8KoaYuICx9+Gg94bM8AEsB7RJNMEjcIZkNFKxKct/VU= X-Google-Smtp-Source: ABdhPJwySX7T5MFquymJzI8106wic63AQbS854elBIICU/OwiKr/Zq9qRw1xF9Y4/kNdKPIsyruvneDm4rIkavqRUag= X-Received: by 2002:a05:6402:5249:: with SMTP id t9mr53787917edd.135.1634648525295; Tue, 19 Oct 2021 06:02:05 -0700 (PDT) MIME-Version: 1.0 References: <577837.1634054018@sss.pgh.pa.us> <20211012232823.GA2342@momjian.us> <17bff549ad836b2a8dc17e8f4fc42202e1424903.camel@cybertec.at> In-Reply-To: <17bff549ad836b2a8dc17e8f4fc42202e1424903.camel@cybertec.at> From: Agil Azimov Date: Tue, 19 Oct 2021 17:01:54 +0400 Message-ID: Subject: Re: Password settings requirements To: Laurenz Albe Cc: Bruce Momjian , Tom Lane , pgsql-novice@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000aed73f05ceb44492" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000aed73f05ceb44492 Content-Type: text/plain; charset="UTF-8" Thank you for the clarification! The issue is that I have to check and report the current state )). Is there any way I can check current password settings (minimal password length for instance and maximum password lifetime). Ideally all of the settings mentioned above ). I appreciate any help you can provide. Warm regards, Agil On Tue, Oct 19, 2021 at 4:20 PM Laurenz Albe wrote: > On Tue, 2021-10-19 at 11:38 +0400, Agil Azimov wrote: > > > > On Wed, Oct 13, 2021 at 3:28 AM Bruce Momjian wrote: > > > On Tue, Oct 12, 2021 at 08:46:44PM +0400, Agil Azimov wrote: > > > > Thank you for your message. Will I be able to set all the settings I > mentioned > > > > before if I will set SCRAM? > > > > > > No. I think you need to use PAM or something like that if you want > > > those requirements. > > > > > Thank you for your reply! I would like to check the current password > requirements of PostgreSQL server. Could you please let me know which > command will show me the > > 1. Minimal requirements for password length > > 2. Maximum password age > > 3. If the password complexity requirements are turned on. > > 4. Password history requirement - number of passwords > > 5. Account lockout threshold. > > > > I appreciate you support. > > As Bruce said, there are no such requirements. > You will have to manage your passwords outside of PostgreSQL if > you need to impose password rules. > PAM, the pluggabla authentication mocule of Linux, is one way of doing > that. > > Yours, > Laurenz Albe > -- > Cybertec | https://www.cybertec-postgresql.com > > --000000000000aed73f05ceb44492 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you for the clarification!=C2=A0 The issue is that I have to check and report the current state )).=C2=A0Is = there any way I can check current password settings (minimal password lengt= h for instance and maximum password lifetime).=C2=A0 Ideally all of the set= tings mentioned above ). I appreciate any help=C2=A0you can provide.

Warm regards,
Agil

On Tue, Oct 19, 2021 at = 4:20 PM Laurenz Albe <lauren= z.albe@cybertec.at> wrote:
On Tue, 2021-10-19 at 11:38 +0400, Agil Azimov wrote:
>
> On Wed, Oct 13, 2021 at 3:28 AM Bruce Momjian <bruce@momjian.us> wrote:
> > On Tue, Oct 12, 2021 at 08:46:44PM +0400, Agil Azimov wrote:
> > > Thank you for your message. Will I be able to set all the se= ttings I mentioned
> > > before if I will set SCRAM?
> >
> > No.=C2=A0 I think you need to use PAM or something like that if y= ou want
> > those requirements.
> >
> Thank you for your reply! I would like to check the current password r= equirements of PostgreSQL server. Could you please let me know which comman= d will show me the
> 1. Minimal requirements for password length
> 2. Maximum password age
> 3. If the password complexity requirements are turned on.
> 4. Password history requirement - number of passwords
> 5. Account lockout threshold.
>
> I appreciate you support.

As Bruce said, there are no such requirements.
You will have to manage your passwords outside of PostgreSQL if
you need to impose password rules.
PAM, the pluggabla authentication mocule of Linux, is one way of doing that= .

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

--000000000000aed73f05ceb44492--