pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Josh Berkus <josh@agliodbs.com>
To: Volker Aßmann <volker.assmann@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Disabling trust/ident authentication configure option
Date: Mon, 18 May 2015 10:36:13 -0500
Message-ID: <555A06ED.3040609@BlueTreble.com> (raw)
In-Reply-To: <55596375.7070601@agliodbs.com>
References: <CA+TgmoYFWGoZVCRVpgwGYSiZhY9PFkC0mrmnYy3acFJ=aU0eEw@mail.gmail.com>
	<554A720F.1030706@dunslane.net>
	<CA+TgmoZMX3FvHnnXcuiTTuh=6WY2uW6=QmRWkkNdUwD1T5Zh6g@mail.gmail.com>
	<554A797B.1010101@dunslane.net>
	<6837.1430946793@sss.pgh.pa.us>
	<WM!166b48023e720856eea587c0ad127e5181882abf659ccd483360b19f27293d1addb1d058c6dbdafcbaa946420b35a64b!@asav-3.01.com>
	<554A9898.9040407@agliodbs.com>
	<20150507150254.GA30322@tamriel.snowman.net>
	<CA+TgmobuF2CdDm=W-gi1XK9OT3kcck511UHigWtC0mus1scGPA@mail.gmail.com>
	<20150507205749.GE30322@tamriel.snowman.net>
	<CA+TgmobkrjWGrP1vnr+D3OmQd68nGYhUsM3k6q3Nn8BJpLXdhg@mail.gmail.com>
	<CAJBpAdwwX8MmHaqMu43YCLJLrpX=1uKAgzpwRBqU8xNX=920Kw@mail.gmail.com>
	<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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

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



view thread (61+ messages)  latest in thread

Message-ID: <555A06ED.3040609@BlueTreble.com>
Permalink:  ../555A06ED.3040609@BlueTreble.com/
Also on:    postgresql.org/message-id/555A06ED.3040609@BlueTreble.com

 · 

reply
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-hackers@postgresql.org
  Cc: Jim.Nasby@BlueTreble.com, josh@agliodbs.com, volker.assmann@gmail.com, sfrost@snowman.net, tgl@sss.pgh.pa.us, andrew@dunslane.net, alvherre@2ndquadrant.com
  Subject: Re: Disabling trust/ident authentication configure option
  In-Reply-To: <555A06ED.3040609@BlueTreble.com>

* 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