Received: from malur.postgresql.org ([2a02:16a8:dc51::56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1fdx3Q-00041A-GQ
	for pgsql-docs@arkaria.postgresql.org; Fri, 13 Jul 2018 12:20:08 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1fdx3O-00026V-Oi
	for pgsql-docs@arkaria.postgresql.org; Fri, 13 Jul 2018 12:20:06 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pinker@onet.eu>)
	id 1fdx3O-00026O-JH
	for pgsql-docs@lists.postgresql.org; Fri, 13 Jul 2018 12:20:06 +0000
Received: from n3.nabble.com ([162.255.23.22])
	by magus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pinker@onet.eu>)
	id 1fdx3L-0005Sw-0c
	for pgsql-docs@postgresql.org; Fri, 13 Jul 2018 12:20:06 +0000
Received: from n3.nabble.com (localhost [127.0.0.1])
	by n3.nabble.com (Postfix) with ESMTP id A1F0CDFE7F19
	for <pgsql-docs@postgresql.org>; Fri, 13 Jul 2018 05:20:00 -0700 (MST)
Date: Fri, 13 Jul 2018 05:20:00 -0700 (MST)
From: pinker <pinker@onet.eu>
To: pgsql-docs@postgresql.org
Message-ID: <1531484400661-0.post@n3.nabble.com>
In-Reply-To: 
 <CAB7nPqStc7BMNaQU52yAOC-b1nhCt_S0mhExF3CvyBALNq509Q@mail.gmail.com>
References: <20170629122330.1478.89209@wrigleys.postgresql.org>
 <CAB7nPqStc7BMNaQU52yAOC-b1nhCt_S0mhExF3CvyBALNq509Q@mail.gmail.com>
Subject: Re: Password encryption
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

Michael Paquier wrote
> 
> A user knowing only the MD5 hash, and not the plain password would
> still be able to connect, so you really had better use SSL anyway if
> connecting with an untrusted network. Postgres 10 comes up with
> SCRAM-SHA-256 by the way, which is stronger by design for such things.

Hi, with untrusted network you mean eavesdropping or some other "evil"
technique?
With normal client like psql or pgAdmin is no way to log in having only md5
hash, right?



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-docs-f2165602.html