Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: PQconnectdbParams and encrypted password
From: Dmitry Markman <dmarkman@mac.com>
In-Reply-To: <14941.1567173032@sss.pgh.pa.us>
Date: Fri, 30 Aug 2019 18:48:47 -0400
Cc: pgsql-interfaces@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AEFA959F-25B1-4550-94C2-27516C062931@mac.com>
References: <67A8E555-D7C6-41D4-B4A7-0B9E2949A6FC@mac.com>
 <14941.1567173032@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk

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@sss.pgh.pa.us> wrote:
>=20
> Dmitry Markman <dmarkman@mac.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 =
=E2=80=98md5f3c33545d22dbf811737afb8d0e85597=E2=80=99
>> ...
>>                {"password", ??????????????},//I=E2=80=99d like to =
have here =E2=80=9Cmd5f3c33545d22dbf811737afb8d0e85597=E2=80=9D, but it =
doesn=E2=80=99t work
>=20
> 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.
>=20
> 			regards, tom lane