| 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-05-28 13:28:26 |
| Message-ID: | ea469142-b3a7-92d3-a5f4-cf372a0ec274@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
Jonathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-05-28 13:42:39 | Re: Explain Analyze (Rollback off) Suggestion |
| Previous Message | Robert Haas | 2020-05-28 13:25:37 | Re: New 'pg' consolidated metacommand patch |