From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: password_encryption, default and 'plain' support |
Date: | 2017-05-03 12:57:26 |
Message-ID: | CABUevEzfCpzJGYve6QWj9PnfCoWNge=sFUvjMTRoBr--Gdmung@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 3, 2017 at 2:25 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:
> On Wed, May 3, 2017 at 8:38 PM, Magnus Hagander <magnus(at)hagander(dot)net>
> wrote:
> > On Wed, May 3, 2017 at 1:31 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
> wrote:
> >> In various threads on SCRAM, we've skirted around the question of
> whether
> >> we should still allow storing passwords in plaintext. I've avoided
> >> discussing that in those other threads, because it's been an orthogonal
> >> question, but it's a good question and we should discuss it.
> >>
> >> 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.
> >
> > Is there any usecase at all for it today?
>
> For developers running applications on top of Postgres?
>
I don't get it. How does password_encryption=plain help them?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | amul sul | 2017-05-03 13:09:15 | Re: [POC] hash partitioning |
Previous Message | Ashutosh Sharma | 2017-05-03 12:44:02 | Re: [HACKERS] Re: BUG #14634: On Windows pg_basebackup should write tar to stdout in binary mode |