From: Stephen Frost <sfrost@snowman.net>
To: Joe Conway <mail@joeconway.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Noah Misch <noah@leadboat.com>
Cc: Magnus Hagander <magnus@hagander.net>
Subject: Re: initdb recommendations
Date: Fri, 24 May 2019 08:19:04 -0400
Message-ID: <20190524121904.GU2480@tamriel.snowman.net> (raw)
In-Reply-To: <17041a05-0e28-f2b1-bf0c-fe375af66b45@joeconway.com>
References: <CABUevExMizVYea9zaHBte66u9KipEgfwcsaE9spfqK9iYRST_g@mail.gmail.com>
<20190406180839.GA1921989@rfd.leadboat.com>
<96389374-9454-d26d-6f79-7c7b15ec14bd@2ndquadrant.com>
<81b36e8b-e27b-ab5d-c4f0-6493771bc0ee@postgresql.org>
<9f46f065-ca80-f637-8c5d-a9877bcd5eab@postgresql.org>
<10093.1558664907@sss.pgh.pa.us>
<20190524023009.GL2480@tamriel.snowman.net>
<df011ad3-f1a3-149e-3489-2d68e6ea21a7@joeconway.com>
<20190524121306.GS2480@tamriel.snowman.net>
<17041a05-0e28-f2b1-bf0c-fe375af66b45@joeconway.com>
Greetings,
* Joe Conway (mail@joeconway.com) wrote:
> On 5/24/19 8:13 AM, Stephen Frost wrote:
> > * Joe Conway (mail@joeconway.com) wrote:
> >> On 5/23/19 10:30 PM, Stephen Frost wrote:
> >> > * Tom Lane (tgl@sss.pgh.pa.us) wrote:
> >> >> "Jonathan S. Katz" <jkatz@postgresql.org> writes:
> >> >> > For now I have left in the password based method to be scram-sha-256 as
> >> >> > I am optimistic about the support across client drivers[1] (and FWIW I
> >> >> > have an implementation for crystal-pg ~60% done).
> >> >>
> >> >> > However, this probably means we would need to set the default password
> >> >> > encryption guc to "scram-sha-256" which we're not ready to do yet, so it
> >> >> > may be moot to leave it in.
> >> >>
> >> >> > So, thinking out loud about that, we should probably use "md5" and once
> >> >> > we decide to make the encryption method "scram-sha-256" by default, then
> >> >> > we update the recommendation?
> >> >>
> >> >> Meh. If we're going to break things, let's break them. Set it to
> >> >> scram by default and let people who need to cope with old clients
> >> >> change the default. I'm tired of explaining that MD5 isn't actually
> >> >> insecure in our usage ...
> >> >
> >> > +many.
> >>
> >> many++
> >>
> >> Are we doing this for pg12? In any case, I would think we better loudly
> >> point out this change somewhere.
> >
> > Sure, we should point it out, but I don't know that it needs to be
> > screamed from the rooftops considering the packagers have already been
> > largely ignoring our defaults here anyway...
>
> Yeah, I thought about that, but anyone not using those packages will be
> in for a big surprise. Don't get me wrong, I wholeheartedly endorse the
> change, but I predict many related questions on the lists, and anything
> we can do to mitigate that should be done.
You think there's someone who builds from the source and just trusts
what we have put in for the defaults in pg_hba.conf..?
I've got a really hard time with that idea...
I'm all for making people aware of it, but I don't think it justifies
being the top item of the release notes or some such. Frankly, anything
that starts with "If you build from source, then..." is already going to
be pretty low impact and therefore low on the list of things we need to
cover in the release notes, et al.
Thanks,
Stephen
Attachments:
signature.asc (application/pgp-signature, 818B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: sfrost@snowman.net, mail@joeconway.com, tgl@sss.pgh.pa.us, jkatz@postgresql.org, peter.eisentraut@2ndquadrant.com, pgsql-hackers@postgresql.org, noah@leadboat.com, magnus@hagander.net
Subject: Re: initdb recommendations
In-Reply-To: <20190524121904.GU2480@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox