From: David Fetter <david@fetter.org>
To: Stephen Frost <sfrost@snowman.net>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: David Steele <david@pgmasters.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Julian Markwort <julian.markwort@uni-muenster.de>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Cc: Valery Popov <v.popov@postgrespro.ru>
Subject: Re: pg_authid.rolpassword format (was Re: Password identifiers, protocol aging and SCRAM protocol)
Date: Tue, 20 Dec 2016 15:29:12 -0800
Message-ID: <20161220232912.GB22538@fetter.org> (raw)
In-Reply-To: <20161220231439.GA18360@tamriel.snowman.net>
References: <CAB7nPqQ28o6ocOdbidOVmxxcKDMP=woZ=hvAVHKKAjAUtjZNyQ@mail.gmail.com>
<ce051da1-cc5a-2a06-a9a8-6a4d0d98bdd1@2ndquadrant.com>
<20161214145723.GJ23417@tamriel.snowman.net>
<9dc32483-b24a-5832-53e0-fb62838f1315@iki.fi>
<20161215134030.GI23417@tamriel.snowman.net>
<CA+TgmoaRtNXf37AfLvhMMsoEP9LdvAvhSOoSm2nDHF72aqdiww@mail.gmail.com>
<5ec22c98-16b9-4d13-a551-9aa46d8f1269@iki.fi>
<20161220133419.GX18360@tamriel.snowman.net>
<20161220160801.GA7806@fetter.org>
<20161220231439.GA18360@tamriel.snowman.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Tue, Dec 20, 2016 at 06:14:40PM -0500, Stephen Frost wrote:
> David,
>
> * David Fetter (david@fetter.org) wrote:
> > On Tue, Dec 20, 2016 at 08:34:19AM -0500, Stephen Frost wrote:
> > > * Heikki Linnakangas (hlinnaka@iki.fi) wrote:
> > > > Even if you have a separate "verifier type" column, it's not fully
> > > > normalized, because there's still a dependency between the
> > > > verifier and verifier type columns. You will always need to look
> > > > at the verifier type to make sense of the verifier itself.
> > >
> > > That's true- but you don't need to look at the verifier, or even
> > > have *access* to the verifier, to look at the verifier type.
> >
> > Would a view that shows only what's to the left of the first semicolon
> > suit this purpose?
>
> Obviously a (security barrier...) view or a (security definer) function
> could be used, but I don't believe either is actually a good idea.
Would you be so kind as to help me understand what's wrong with that idea?
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: david@fetter.org, sfrost@snowman.net, hlinnaka@iki.fi, robertmhaas@gmail.com, peter.eisentraut@2ndquadrant.com, michael.paquier@gmail.com, andres@anarazel.de, david@pgmasters.net, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, magnus@hagander.net, julian.markwort@uni-muenster.de, v.popov@postgrespro.ru
Subject: Re: pg_authid.rolpassword format (was Re: Password identifiers, protocol aging and SCRAM protocol)
In-Reply-To: <20161220232912.GB22538@fetter.org>
* 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