Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YuN5g-00019g-N0 for pgsql-hackers@arkaria.postgresql.org; Mon, 18 May 2015 15:36:28 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YuN5g-0006uH-7G for pgsql-hackers@arkaria.postgresql.org; Mon, 18 May 2015 15:36:28 +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 1YuN5f-0006uB-2q for pgsql-hackers@postgresql.org; Mon, 18 May 2015 15:36:27 +0000 Received: from mail-bl2on0093.outbound.protection.outlook.com ([65.55.169.93] helo=na01-bl2-obe.outbound.protection.outlook.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1YuN5b-0000hR-RH for pgsql-hackers@postgresql.org; Mon, 18 May 2015 15:36:25 +0000 Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=Jim.Nasby@bluetreble.com; Received: from decina.attlocal.net (2602:306:ce8b:3460:d4d2:6316:34b5:c64b) by BLUPR11MB0675.namprd11.prod.outlook.com (25.163.216.145) with Microsoft SMTP Server (TLS) id 15.1.166.22; Mon, 18 May 2015 15:36:17 +0000 Message-ID: <555A06ED.3040609@BlueTreble.com> Date: Mon, 18 May 2015 10:36:13 -0500 From: Jim Nasby User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Josh Berkus , =?UTF-8?B?Vm9sa2VyIEHDn21hbm4=?= CC: Stephen Frost , Tom Lane , Andrew Dunstan , Alvaro Herrera , "pgsql-hackers@postgresql.org" Subject: Re: Disabling trust/ident authentication configure option References: <554A720F.1030706@dunslane.net> <554A797B.1010101@dunslane.net> <6837.1430946793@sss.pgh.pa.us> <554A9898.9040407@agliodbs.com> <20150507150254.GA30322@tamriel.snowman.net> <20150507205749.GE30322@tamriel.snowman.net> <55596375.7070601@agliodbs.com> In-Reply-To: <55596375.7070601@agliodbs.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [2602:306:ce8b:3460:d4d2:6316:34b5:c64b] X-ClientProxiedBy: DM2PR10CA0069.namprd10.prod.outlook.com (10.141.241.37) To BLUPR11MB0675.namprd11.prod.outlook.com (25.163.216.145) X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR11MB0675; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:BLUPR11MB0675; BCL:0; PCL:0; RULEID:; SRVR:BLUPR11MB0675; X-Forefront-PRVS: 058043A388 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(199003)(377454003)(24454002)(479174004)(189002)(122386002)(106356001)(105586002)(5001860100001)(46102003)(5001830100001)(53416004)(33656002)(42186005)(40100003)(81156007)(4001540100001)(101416001)(92566002)(36756003)(93886004)(4001350100001)(97736004)(15975445007)(68736005)(2950100001)(77156002)(19580395003)(62966003)(64126003)(80316001)(76176999)(65816999)(50986999)(86362001)(23676002)(59896002)(87266999)(54356999)(83506001)(5001960100002)(50466002)(5001770100001)(65806001)(69596002)(47776003)(64706001)(87976001)(65956001)(189998001)(3826002)(85282002)(336755003)(18886065003); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR11MB0675; H:decina.attlocal.net; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received-SPF: None (protection.outlook.com: bluetreble.com does not designate permitted sender hosts) X-OriginatorOrg: bluetreble.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 May 2015 15:36:17.2765 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR11MB0675 X-Pg-Spam-Score: -3.0 (---) 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 On 5/17/15 10:58 PM, Josh Berkus wrote: > The goal here was stated to preventing authentication misconfiguration > by shortsighted admins who have superuser access and the ability to > change pg_hba.conf. This is tantamount to giving someone a gun and > bullets, but expecting duct tape across the cartridge slot to prevent > them from loading or using the gun. The idea is to prevent *accidental* misconfiguration, not to try and permanently lock them out. IE: make them think before allowing them to just do something silly. Disabling auth methods at compile time seems a very reasonable way to accomplish that. -- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers