From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> |
Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: scram-sha-256 encrypted password in pgpass |
Date: | 2020-06-22 22:43:51 |
Message-ID: | CAKFQuwYHDX1FU-rBzv9GXR_9P6dJpryFfUUgZ1bG4xT_8ZqiDQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Mon, Jun 22, 2020 at 3:32 PM Pavan Kumar <pavan(dot)dba27(at)gmail(dot)com> wrote:
> Adrian, David,
>
> Thank you so much for the quick response.
>
> What would be the point of storing the encrypted password instead of the
> plaintext one?
> As per our organization security policies, we can 't keep any passwords
> in plain text format.
> I am working on postgres + pgbouncer setup, tested pgbouncer 1.14 where we
> have support to use encrypted password in userlist,txt file. I am
> surprised why pgpass is not supporting encrypted passwords.
>
>
Just use a long string of random letters, numbers, and symbols and say its
encrypted...
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2020-06-22 22:54:37 | Re: scram-sha-256 encrypted password in pgpass |
Previous Message | Adrian Klaver | 2020-06-22 22:36:18 | Re: scram-sha-256 encrypted password in pgpass |
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2020-06-22 22:54:37 | Re: scram-sha-256 encrypted password in pgpass |
Previous Message | Adrian Klaver | 2020-06-22 22:36:18 | Re: scram-sha-256 encrypted password in pgpass |