| From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vik Fearing <vik(at)postgresfriends(dot)org> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: password_encryption default |
| Date: | 2020-06-10 14:51:22 |
| Message-ID: | 492faf93-33b4-1244-a4af-ddcee15bc8d4@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/10/20 10:47 AM, Peter Eisentraut wrote:
> On 2020-05-28 15:28, Jonathan S. Katz wrote:
>> On 5/28/20 8:10 AM, Peter Eisentraut wrote:
>>> On 2020-05-27 15:25, Jonathan S. Katz wrote:
>>>> $ initdb -D data --auth-local=scram-sha-256 --auth-host=md5
>>>>
>>>> Got an error message:
>>>>
>>>> "initdb: error: must specify a password for the superuser to enable md5
>>>> authentication"
>>>>
>>>> For the last two, that behavior is to be expected (after all, you've
>>>> set
>>>> the two login vectors to require passwords), but the error message
>>>> seems
>>>> odd now. Perhaps we tweak it to be:
>>>>
>>>>
>>>> "initdb: error: must specify a password for the superuser when
>>>> requiring
>>>> passwords for both local and host authentication."
>>>
>>> That message is a bit long. Maybe just
>>>
>>> must specify a password for the superuser to enable password
>>> authentication
>>>
>>> without reference to the specific method. I think the idea is clear
>>> there.
>>
>> +1
>
> committed
Yay!!! Thank you!
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2020-06-10 16:18:55 | Re: Recording test runtimes with the buildfarm |
| Previous Message | Peter Eisentraut | 2020-06-10 14:47:42 | Re: password_encryption default |