Date: Wed, 20 May 2015 14:09:17 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Josh Berkus <josh@agliodbs.com>,
 Volker =?iso-8859-1?Q?A=DFmann?= <volker.assmann@gmail.com>,
 Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
 Andrew Dunstan <andrew@dunslane.net>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: Disabling trust/ident authentication configure option
Message-ID: <20150520180917.GL26667@tamriel.snowman.net>
References: 
 <CA+Tgmob4wt1f84k-iYPou1ZtHCwLn=gRApk4i=q8TAwnQjCx+w@mail.gmail.com>
 <CAJBpAdxWQscGEJubs-KLMXYd76tspwD_b2wmgYArsYYTX5ao7w@mail.gmail.com>
 <WM!3b761876ad683334d7afacc13949867067da229b8b4a89a6384ebd101a9ce056b35e6732803f2295acef5787aadcb6e2!@asav-1.01.com>
 <55596375.7070601@agliodbs.com>
 <CAJBpAdzUeVqJ1R+0V_Eg8+Z0HdrHYq7HHx+a4q1BT9-h9Yvoiw@mail.gmail.com>
 <CB1A1AB6-B345-4ED7-A705-D87E4DC99E11@gmail.com>
 <CAJBpAdzH3pMTFfBE+dYd+OytVJXR2XF=ESQ7TG6syjB1suh2ZQ@mail.gmail.com>
 <WM!22b0c9d0d605588edea2c700c71c4e0b51033b37a1185be38d4160d6de08c76eba51fd2754a9d1446b4cfb3fccceb9ce!@asav-2.01.com>
 <555CC5DE.3050707@agliodbs.com>
 <20150520175916.GB5885@postgresql.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="W4pDZ/VvazBYHhxQ"
Content-Disposition: inline
In-Reply-To: <20150520175916.GB5885@postgresql.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


--W4pDZ/VvazBYHhxQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> Josh Berkus wrote:
>=20
> > As such, proposals are more likely to be successful if the proposer can
> > show how they apply to a general use case, or adapt them so that they
> > are useful to a large number of our users.  This means that "this works
> > in our environment which has conditions X, Y, and Z" is not an effective
> > argument, unless you can follow it up with "... and here's the reason
> > why [large class of users] also has conditions X, Y and Z."
>=20
> The proposal here is to have a configure argument that disables
> arbitrary auth mechanisms.  How is that specific to a particular
> environment?

For my 2c, I'm still a fan of the general idea..  I still view 'trust'
as appropriate only for development environments and I don't believe it
really solves any use-cases that having password-less accounts doesn't.

Removing it as an option simply removes a potential configuration
mistake.  It's not going to protect you from a malicious administrator
who has root-level access any more than a CHECK constraint would stop a
malicious DBA.

	Thanks!

		Stephen

--W4pDZ/VvazBYHhxQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVXM3NAAoJEO1sijiDR2RVUA0P/jAwAlRN18nESWuQo7MeVe+J
qpYn7a3/F9lIqr7B/oav2O9QBX3qJHsQU2JC4krES1G6RRI8gMRSVkc3n7W6WsUX
qhsUNbGIjo3/eELikc+de6M41SlM5pq53lBkGPJeTh0sdlul3HlmsVhkTy4/99ON
kE2ezof4TmePM8SciETtnpBTKfzVr+MtzPHM6WBAoz3rVda5xvQXlDSDWF2wh7/A
sWuP2429mNCiVLTnbsMBUL+kxHV3dsnx3zXGdg6d4qapeZylfVumDQszexlz+r8o
SimOgKJhNagnCBTUtWsZNIoMPgEqkS93lHfk4qXkcaHRyB7nkDdglbLDXwMFqDqj
lxylVqZaEtipq/j+lMjoqKsgRIHNH5flbYdob/T1BTEo3XXDGzekL1MAO3seTCBF
v3ZieeeEIDxGZg5E974LYHKYXQ7m7sW2WzT2mkpZEoMEhnorxdeoqVMjsMoKOCF4
cU44C1Ve7mhoCK1XqxVofHU6OH/xTzymcuplrLIDXu5IroJEUr0eCHPsmNThnsaA
HBIrNQgRA5Do0/u9m0gLZYvW/AJQyCU6gMqJ7Kq+YDhbdnbnymk6gDb1VSjTr5fd
4lU0ToQZOAQc4AeBh/UnaW3ODt4hRafvuoFoAsxTrh7bPm2WWeqDnSZgByCzC4qB
7FpmMg1edAzPIq6IkFLr
=hwk2
-----END PGP SIGNATURE-----

--W4pDZ/VvazBYHhxQ--