pgsql: Remove bogus notice that older clients might not work with MD5 p

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Remove bogus notice that older clients might not work with MD5 p
Date: 2017-01-03 12:11:20
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Remove bogus notice that older clients might not work with MD5 passwords.

That was written when we still had "crypt" authentication, and it was
referring to the fact that an older client might support "crypt"
authentication but not "md5". But we haven't supported "crypt" for years.
(As soon as we add a new authentication mechanism that doesn't work with
MD5 hashes, we'll need a similar notice again. But this text as it's worded
now is just wrong.)

Backpatch to all supported versions.

Discussion: https://www.postgresql.org/message-id/[email protected]

Branch
------
REL9_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/ada2cdb61015e6baed5bd9fcce7fa4985147b27d

Modified Files
--------------
doc/src/sgml/ref/create_role.sgml | 6 ------
1 file changed, 6 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-01-03 14:29:10 pgsql: Fix hot standby tests for sequence catalog change
Previous Message Tom Lane 2017-01-03 02:37:35 pgsql: Allow SSL configuration to be updated at SIGHUP.