Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yv8HX-0004co-3x for pgsql-hackers@arkaria.postgresql.org; Wed, 20 May 2015 17:59:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yv8HW-00082s-LO for pgsql-hackers@arkaria.postgresql.org; Wed, 20 May 2015 17:59:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Yv8HV-00082k-7f for pgsql-hackers@postgresql.org; Wed, 20 May 2015 17:59:49 +0000 Received: from mail-qk0-f175.google.com ([209.85.220.175]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Yv8HR-0007x4-KE for pgsql-hackers@postgresql.org; Wed, 20 May 2015 17:59:48 +0000 Received: by qkgv12 with SMTP id v12so37095136qkg.0 for ; Wed, 20 May 2015 10:59:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=mQ9A38kB/mbTrKGjyUeYK2LBRQgRlI47F7qw3xMhWAQ=; b=ZXB8oDr2ykEZo9WdNF45AwOtfmNGBoM4YuSBA7Ko+VdG5FUsBoGGydYc3AM+DyEJxS tPKrG1gT8hjzBkWqEi1B3JKKYPklMogJiayg2WDbNtz+LxzmybnSlaF9LwFeYUuvvTDE ozYSjKDXXmeckFKdegK6Qd4sTOfiO0xLQSRQ+D+Azasy6VUvKVoSipiNcTcXLzPQt+Xp iGj60jSh/SdFPO+oImolbJ/BA9/Xn8fVENlyGNDDVlBKV+g3on9+Y5nhpLpZxUhPBkmZ BkYSJw0AkER4b1rN5O2SI6ts9DjGUWxSBMlUZesTGQuFjCmCI4kS4U7PAOelgnKcu2zo bpUA== X-Gm-Message-State: ALoCoQn5YhXyNzcHVqFDFPprL/E2LHR9WR7jv18atHY48DbcYsw6pg0Ib5uXLLoxcaRybg3tn/pm X-Received: by 10.55.21.224 with SMTP id 93mr75900733qkv.89.1432144783115; Wed, 20 May 2015 10:59:43 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([186.37.26.179]) by mx.google.com with ESMTPSA id k19sm11616407qgd.3.2015.05.20.10.59.42 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 May 2015 10:59:42 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id DAD9654A; Wed, 20 May 2015 14:59:16 -0300 (CLT) Date: Wed, 20 May 2015 14:59:16 -0300 From: Alvaro Herrera To: Josh Berkus Cc: Volker =?iso-8859-1?Q?A=DFmann?= , Robert Haas , Stephen Frost , Tom Lane , Andrew Dunstan , "pgsql-hackers@postgresql.org" Subject: Re: Disabling trust/ident authentication configure option Message-ID: <20150520175916.GB5885@postgresql.org> References: <55596375.7070601@agliodbs.com> <555CC5DE.3050707@agliodbs.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <555CC5DE.3050707@agliodbs.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -3.7 (---) 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 Josh Berkus wrote: > 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." The proposal here is to have a configure argument that disables arbitrary auth mechanisms. How is that specific to a particular environment? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers