Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YvDgt-0002XN-9C for pgsql-hackers@arkaria.postgresql.org; Wed, 20 May 2015 23:46:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YvDgs-0001hi-I2 for pgsql-hackers@arkaria.postgresql.org; Wed, 20 May 2015 23:46:22 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YvDgq-0001hb-VH for pgsql-hackers@postgresql.org; Wed, 20 May 2015 23:46:21 +0000 Received: from tamriel.snowman.net ([2001:4830:167b::11]) by makus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1YvDgj-0006yi-KI for pgsql-hackers@postgresql.org; Wed, 20 May 2015 23:46:19 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id C23C55F799; Wed, 20 May 2015 19:46:12 -0400 (EDT) Date: Wed, 20 May 2015 19:46:12 -0400 From: Stephen Frost To: Andres Freund Cc: Josh Berkus , Tom Lane , Alvaro Herrera , Volker =?iso-8859-1?Q?A=DFmann?= , Robert Haas , Andrew Dunstan , "pgsql-hackers@postgresql.org" Subject: Re: Disabling trust/ident authentication configure option Message-ID: <20150520234612.GO26667@tamriel.snowman.net> References: <555CC5DE.3050707@agliodbs.com> <20150520175916.GB5885@postgresql.org> <23809.1432145430@sss.pgh.pa.us> <555CDC56.5050607@agliodbs.com> <20150520194223.GM26667@tamriel.snowman.net> <20150520215444.GR27868@alap3.anarazel.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="U0B5otXy6WXfork9" Content-Disposition: inline In-Reply-To: <20150520215444.GR27868@alap3.anarazel.de> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/3.13.0-46-generic (x86_64) X-Uptime: 19:41:46 up 62 days, 5:30, 11 users, load average: 0.08, 0.04, 0.05 User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org --U0B5otXy6WXfork9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Andres, * Andres Freund (andres@anarazel.de) wrote: > On 2015-05-20 15:42:23 -0400, Stephen Frost wrote: > > > So the first thing to establish is "other than Volker himself, who are > > > we helping here?" > >=20 > > I don't agree with this either. Providing a "bypass all authentication" > > configuration option really isn't a good thing. Why don't packagers use > > our default pg_hba.conf? Because it only makes sense in a development > > type of environment. I'd argue the same is true for 'trust'. >=20 > Uh. So if the shit hit the fan because you mismanaged a password > rollover, kereberos is down, or something like that, and you can't > access postgres anymore you want to recompile? And no peer isn't an > answer isn't an answer, it's not available on windows. Your only way out > is going to be single user mode. But wait, that's a security hole too. Apologies for not being clearer. I agree that we need an alternative for addressing this use-case before we can consider getting rid of 'trust' or not having it built into the binaries which are distributed. In other words, I agree with you that we can't simply get rid of 'trust' without having another solution. I *do* believe that a real single-user mode that is only available to the owner of the cluster would go a long way towards this goal. If 'trust' was only able to be used by the owner of the database, I'd have much less of an issue with it. > I find the arguments presented in this thread for a configure option > entirely unconvincing. If you'd argued for a saner default > authentication setup: I'd be on board with that. But this seems just a > pointless exercise in making things more complicated. Thankfully, the packagers have already addressed the insecure default that the source build provides for pg_hba.conf and so we don't need to worry about it (except perhaps for new distributions or new packagers, but I hope they'll usually look at the existing packages and not just distribute what we provide as the default pg_hba.conf). Thanks! Stephen --U0B5otXy6WXfork9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJVXRzEAAoJEO1sijiDR2RV31EP/1hdKOvbwg+rKqYSVzeS3GSY /DH1dORs1QzI8HjiDqc8HgFkrh5wFXOwMqKNy+Yhemkh9zJBy4zpV8AtSqYFckNJ YNNAFMawpc5ufZuCvQPh1CXRQD88JZUkEX37SSrw/QdzQmuVO//rDi+YHCDDMIbj rl0tOJRg5A+X2jbfACkbbE2od2i4Ojl7nOo+iOTsYahT8a8JtYNVmISsnOuWLsuJ 3Py3ZWhEjNUPJXfsbzGja5zKdVdbB9zlKIxpNHpkCfzaszYUk/rl3cZNf8hUXxNp /FFGokXZPFTase0eatCgrXXAB9KOgT3EpJe4dlWzEk+fAvkNeAQwBQC+PeWNEvGi 5WbetqmaW+OYJtN5AhXXNaxwbgC2RvrQ79naQJNaNn8I0i8vF/oShBP5x5XkPKri RR1q36fuCfSkBVVc7/it3kYdxxf3PZb1ZWV9T+h2fspHpSv3ItGPAoPSSVCdwb5g P45avnq9PXfyanxOj23HxiUpovZvv/uddQcQOWm1fY5CXB8n6gZ+eSvSXryUK49e emBv4vf32yPPk56kNGRrtfDvCzKLG6i12DfxmGCKmltPf37872Yf8udxzicKOjXP 69/oDrU9rWHi0Dj3g1LlKEe2RT1ek3hhdoDCuTKyMkgFxtxLGoSvlfnCtpcvg1Fr zMbA0Y5LLTlHINtivB1Q =3RE0 -----END PGP SIGNATURE----- --U0B5otXy6WXfork9--