From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Markman <dmarkman@mac.com>
cc: pgsql-interfaces@lists.postgresql.org
Subject: Re: PQconnectdbParams and encrypted password
In-reply-to: <67A8E555-D7C6-41D4-B4A7-0B9E2949A6FC@mac.com>
References: <67A8E555-D7C6-41D4-B4A7-0B9E2949A6FC@mac.com>
Comments: In-reply-to Dmitry Markman <dmarkman@mac.com>
	message dated "Fri, 30 Aug 2019 00:19:15 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <14940.1567173032.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 30 Aug 2019 09:50:32 -0400
Message-ID: <14941.1567173032@sss.pgh.pa.us>
Precedence: bulk

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=98md5f3c33545d22dbf811=
737afb8d0e85597=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

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