md5 still listed as an option in pg_hba.conf.sample
The comment that I think needs updating is:
# METHOD can be "trust", "reject", "md5", "password", "scram-sha-256",
# "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert".
The "md5" option no longer works, as discussed in other threads.
mark
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Sep 26, 2017 at 1:23 PM, Mark Dilger <hornschnorter@gmail.com> wrote:
The comment that I think needs updating is:
# METHOD can be "trust", "reject", "md5", "password", "scram-sha-256",
# "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert".The "md5" option no longer works, as discussed in other threads.
It works for me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Sep 26, 2017 at 10:23:55AM -0700, Mark Dilger wrote:
The comment that I think needs updating is:
# METHOD can be "trust", "reject", "md5", "password", "scram-sha-256",
# "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert".The "md5" option no longer works, as discussed in other threads.
Uh, I think that "md5" still works just fine.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sep 26, 2017, at 10:36 AM, Bruce Momjian <bruce@momjian.us> wrote:
On Tue, Sep 26, 2017 at 10:23:55AM -0700, Mark Dilger wrote:
The comment that I think needs updating is:
# METHOD can be "trust", "reject", "md5", "password", "scram-sha-256",
# "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert".The "md5" option no longer works, as discussed in other threads.
Uh, I think that "md5" still works just fine.
Yes, sorry for the noise.
I was under the impression that md5 was removed for this release, per other
threads that I must not have followed closely enough.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, Sep 27, 2017 at 2:41 AM, Mark Dilger <hornschnorter@gmail.com> wrote:
I was under the impression that md5 was removed for this release, per other
threads that I must not have followed closely enough.
md5 is still present, its configuration in pg_hba.conf and
password_encryption are still here. "plain" is what has been removed.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On 9/26/17 18:39, Michael Paquier wrote:
On Wed, Sep 27, 2017 at 2:41 AM, Mark Dilger <hornschnorter@gmail.com> wrote:
I was under the impression that md5 was removed for this release, per other
threads that I must not have followed closely enough.md5 is still present, its configuration in pg_hba.conf and
password_encryption are still here. "plain" is what has been removed.
More precisely, the ability to store passwords in plain text in
pg_authid has been removed. You can still use the authentication method
"password" that sends passwords in plain text over the wire.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers