Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YuRCs-00052j-FF for pgsql-hackers@arkaria.postgresql.org; Mon, 18 May 2015 20:00:10 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YuRCr-0004b4-Sl for pgsql-hackers@arkaria.postgresql.org; Mon, 18 May 2015 20:00:09 +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 1YuRCq-0004ao-Pt for pgsql-hackers@postgresql.org; Mon, 18 May 2015 20:00:08 +0000 Received: from mail-qk0-f177.google.com ([209.85.220.177]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1YuRCn-0005IQ-5v for pgsql-hackers@postgresql.org; Mon, 18 May 2015 20:00:08 +0000 Received: by qkgw4 with SMTP id w4so76522349qkg.3 for ; Mon, 18 May 2015 13:00:02 -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=9aDGnTVaOHgz2r2PaWFEEMXRokjip7cEOWOHNMs2UQ8=; b=m6UR6O5KdTMjwoj1IwfCwtZKp4yLWbyz4DPqgNS4wfDMg4/Cl04sqf8tELiezRbHx5 eXL+32IAtIpoeMVhowgx/iksF1JvHKRUpiyCzcQ+gmfPjYuq7vTdNoRCyY1he8kI93v+ ccmB5erave01TijCDpTW0fwUifZbEqy46TFufKuQNVupTXa+tlMirGON7eEkH9kpRSkF C+ChXGNVt0QBbcp3eMlHN+a5H0gi1aAxt6Sr2Or1hRmVWCxWHXyvUScz3u45F9/iJsIF 0c+2d/x/KVnG6PTE99fT3ltXqKxz47ZF3IteIUsc2/Hru2U/zrW5LILdeshI0/40l6lJ EBgA== X-Gm-Message-State: ALoCoQkLnaLgKIj83AAqyllsPt/FOgVosBJ+oCwC/d1c901Z37lsa/zjLE1BHSnvkHl4pgiyPWOR X-Received: by 10.55.40.132 with SMTP id o4mr51724270qko.61.1431979202746; Mon, 18 May 2015 13:00:02 -0700 (PDT) Received: from alvin.alvh.no-ip.org ([186.37.57.236]) by mx.google.com with ESMTPSA id i106sm7643763qgi.30.2015.05.18.13.00.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 May 2015 13:00:02 -0700 (PDT) Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000) id EFFF9879; Mon, 18 May 2015 17:00:41 -0300 (CLT) Date: Mon, 18 May 2015 17:00:41 -0300 From: Alvaro Herrera To: Bruce Momjian Cc: Volker =?iso-8859-1?Q?A=DFmann?= , Josh Berkus , Stephen Frost , Tom Lane , Andrew Dunstan , "pgsql-hackers@postgresql.org" Subject: Re: Disabling trust/ident authentication configure option Message-ID: <20150518200041.GT2523@alvh.no-ip.org> References: <20150507205749.GE30322@tamriel.snowman.net> <55596375.7070601@agliodbs.com> <20150518195530.GH9458@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150518195530.GH9458@momjian.us> User-Agent: Mutt/1.5.23 (2014-03-12) X-Pg-Spam-Score: -2.6 (--) 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 Bruce Momjian wrote: > On Mon, May 18, 2015 at 09:32:23PM +0200, Volker Aßmann wrote: > > But I like the more general approach proposed by Alvaro, so in case this patch > > would have a chance to not be immediately rejected, I would try to implement > > the more generic approach. I would also include a check to ensure at least one > > reasonably secure way for password recovery is available. For Unix systems > > "peer" authentication seems to be a good candidate. > > Likely to be rejected. Why? -- Á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