|From:||"Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>|
|To:||Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org>|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Given some of the recent hubbub and analysis of CVE entries, one part of
the documentation that could be further clarified is what initdb does
by default, i.e. creates a cluster where users can connect with trust
authentication. While this may be great for people who are hacking or
running PostgreSQL in a trusted local environment, this may not make
sense for many (most?) other systems.
The attached patch clarifies this fact and adds a "warning" box just
below the initdb examples that provides recommendations to create a more
secure environment. It also removes the section that discusses this
below the part that discusses securing the directory, as really this
explanation should go right after the "initdb" call.
(There could be an additional discussion about whether or not we want to
change the default behavior for initdb, but I would suggest that a safe
starting point would be to ensure we call this out)
Credits to Magnus for pointing this out, and Tom + Andrew D. for review
before posting to list.
|Next Message||Peter Eisentraut||2019-04-05 20:58:11||Re: initdb recommendations|
|Previous Message||Daniel Gustafsson||2019-04-05 14:23:22||Re: Clarification to pg_upgrade docs on reverting to old cluster|
|Next Message||Thibaut||2019-04-05 16:12:12||Re: selecting from partitions and constraint exclusion|
|Previous Message||Robbie Harwood||2019-04-05 15:31:25||Re: [PATCH v20] GSSAPI encryption support|