Re: [HACKERS] password_encryption, default and 'plain' support - Mailing list pgsql-hackers

From Albe Laurenz
Subject Re: [HACKERS] password_encryption, default and 'plain' support
Date
Msg-id A737B7A37273E048B164557ADEF4A58B53A348EA@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: [HACKERS] password_encryption, default and 'plain' support  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] password_encryption, default and 'plain' support  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> On Wed, May 3, 2017 at 7:31 AM, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>>> So, I propose that we remove support for password_encryption='plain' in
>>> PostgreSQL 10. If you try to do that, you'll get an error.

>> I have no idea how widely used that option is.

> Is it possible that there are still client libraries that don't support
> password encryption at all?  If so, are we willing to break them?
> I'd say "yes" but it's worth thinking about.

We have one application that has been reduced to "password" authentication
ever since "crypt" authentication was removed, because they implemented the
line protocol rather than using libpq and never bothered to move to "md5".

But then, it might be a good idea to break this application, because that
would force the vendor to implement something that is not a
blatant security problem.

Yours,
Laurenz Albe


pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] Change GetLastImportantRecPtr's definition? (wasSkipcheckpoints, archiving on idle systems.)
Next
From: Amit Kapila
Date:
Subject: Re: [HACKERS] [PROPOSAL] Use SnapshotAny in get_actual_variable_range