| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, 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 12:10:33 |
| Message-ID: | 9ef1c127-12c9-d5d7-0b3f-e435a74b84ce@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-05-28 12:53:17 | Re: password_encryption default |
| Previous Message | Amit Kapila | 2020-05-28 11:52:13 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |