pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: pinker <pinker@onet.eu>
To: pgsql-docs@postgresql.org
Subject: Re: Password encryption
Date: Fri, 13 Jul 2018 05:20:00 -0700 (MST)
Message-ID: <1531484400661-0.post@n3.nabble.com> (raw)
In-Reply-To: <CAB7nPqStc7BMNaQU52yAOC-b1nhCt_S0mhExF3CvyBALNq509Q@mail.gmail.com>
References: <20170629122330.1478.89209@wrigleys.postgresql.org>
	<CAB7nPqStc7BMNaQU52yAOC-b1nhCt_S0mhExF3CvyBALNq509Q@mail.gmail.com>

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

view thread (3+ messages)

Message-ID: <1531484400661-0.post@n3.nabble.com>
Permalink:  ../1531484400661-0.post@n3.nabble.com/
Also on:    postgresql.org/message-id/1531484400661-0.post@n3.nabble.com

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: pinker@onet.eu
  Subject: Re: Password encryption
  In-Reply-To: <1531484400661-0.post@n3.nabble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox