From: | Dmitry Markman <dmarkman(at)mac(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-interfaces(at)lists(dot)postgresql(dot)org |
Subject: | Re: PQconnectdbParams and encrypted password |
Date: | 2019-08-30 22:48:47 |
Message-ID: | AEFA959F-25B1-4550-94C2-27516C062931@mac.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
Hi Tom
thanks a lot for your answer
I realized it almost immediately after I press the button send :)
thanks again
dm
> On Aug 30, 2019, at 9:50 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Dmitry Markman <dmarkman(at)mac(dot)com> writes:
>> I need some help with setting PQconnectdbParams key/value for encrypted password
>> suppose I created user with the string
>> create user foobar with encrypted password ‘md5f3c33545d22dbf811737afb8d0e85597’
>> ...
>> {"password", ??????????????},//I’d like to have here “md5f3c33545d22dbf811737afb8d0e85597”, but it doesn’t work
>
> Pretty much the entire *point* of an encrypted password is that the
> md5 hash is not sufficient to log in with. You need the original
> string.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Malcolm Matalka | 2019-09-03 20:01:28 | Object IDs in Parse message |
Previous Message | Tom Lane | 2019-08-30 13:50:32 | Re: PQconnectdbParams and encrypted password |