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: | E1cONw0-0005cE-Tf@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | 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/9a7263eb-0980-2072-4424-440bb2513dc7@iki.fi
Branch
------
REL9_2_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/7e3ae545594874d853e358fffe029c6266509727
Modified Files
--------------
doc/src/sgml/ref/create_role.sgml | 6 ------
1 file changed, 6 deletions(-)
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. |