Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aV8SK-0006NM-3m for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Feb 2016 02:00:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aV8SJ-0000kc-Md for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Feb 2016 02:00:03 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aV8Qy-00076d-Is for pgsql-hackers@postgresql.org; Mon, 15 Feb 2016 01:58:40 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aV8Qw-0005YG-54 for pgsql-hackers@postgresql.org; Mon, 15 Feb 2016 01:58:39 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u1F1wHWp006175; Sun, 14 Feb 2016 20:58:17 -0500 From: Tom Lane To: Stephen Frost cc: Michael Paquier , David Steele , Heikki Linnakangas , Bruce Momjian , Greg Stark , Robert Haas , Josh Berkus , Peter Eisentraut , pgsql-hackers Subject: Re: WIP: SCRAM authentication In-reply-to: <20160215015110.GL3331@tamriel.snowman.net> References: <20150905003147.GD21484@momjian.us> <56BE1ECD.3020905@pgmasters.net> <20160215001725.GH3331@tamriel.snowman.net> <20160215005640.GI3331@tamriel.snowman.net> <20160215012326.GK3331@tamriel.snowman.net> <5746.1455500723@sss.pgh.pa.us> <20160215015110.GL3331@tamriel.snowman.net> Comments: In-reply-to Stephen Frost message dated "Sun, 14 Feb 2016 20:51:10 -0500" Date: Sun, 14 Feb 2016 20:58:17 -0500 Message-ID: <6174.1455501497@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 Stephen Frost writes: > * Tom Lane (tgl@sss.pgh.pa.us) wrote: >> How about we just say that the password in these old views always reads >> out as '********' even when there is a password, and we invent new views >> that carry real auth information? (Hopefully in an extensible way.) > I'd be alright with that approach, I'd just rather that any clients > which actually want to read the password field be updated to look at the > extensible and sensible base catalogs, and not some hacked up array that > we shoved into that field. Yeah, I'm good with that. I just don't think the breakage needs to extend to clients that aren't trying to read auth-related information. BTW, if we haven't learned this lesson by now: I'm pretty sure that every single one of these views is an attempt to emulate what *used* to be the real base catalog, in some previous release. Maybe we should stop expecting clients to read the real catalog, ever, in favor of a sanitized view? Although I don't know exactly what that would lead to in terms of what we'd expose that's different from what the base catalog is. But it's worth thinking about whether there is a way to avoid having this same discussion again in five or ten years. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers