From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-hackers@postgresql.org
Subject: Re: function body actors (was: [PERFORM] viewing source code)
Date: Fri, 21 Dec 2007 15:56:19 -0500
Message-ID: <20071221205619.GD3864@crankycanuck.ca> (raw)
In-Reply-To: <10257.1198263464@sss.pgh.pa.us>
References: <b42b73150712202109u26d05d01q4f1b8be8d29f763c@mail.gmail.com>
<26811.1198215605@sss.pgh.pa.us>
<20071221164826.GI10918@crankycanuck.ca>
<b42b73150712210948g42498150h976c0b972d632faa@mail.gmail.com>
<10257.1198263464@sss.pgh.pa.us>
On Fri, Dec 21, 2007 at 01:57:44PM -0500, Tom Lane wrote:
> "Merlin Moncure" <mmoncure@gmail.com> writes:
> > ISTM the main issue is how exactly the authenticated user interacts
> > with the actor to give it the information it needs to get the real
> > key. This is significant because we don't want to be boxed into an
> > actor implementation that doesn't allow that interaction.
>
> We don't? What purpose would such a setup serve? I would think
> that for the applications we have in mind, the *last* thing you
> want is for the end user to hold the key. The whole point of this
> is to keep him from seeing the function source code, remember?
Hmm; this may be exactly part of the problem, though. It seems there are
two possible cases in play:
1. Protect the content in the database (in this case, function bodies)
from _all_ users on a given server. This is a case where you want to
protect (say) your function body from your users, because you have a
closed-source application.
2. Protect the content of a field from _some_ users on a given system,
based on the permissions they hold. This is roughly analagous to others not
being able to look in the table I created, because I haven't GRANTed them
permission.
(2) is really a case for column-level access controls, I guess. But if
we're trying to solve this problem too, then user passwords or something
make sense.
A
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-performance@postgresql.org
Cc: ajs@crankycanuck.ca, pgsql-hackers@postgresql.org
Subject: Re: function body actors (was: [PERFORM] viewing source code)
In-Reply-To: <20071221205619.GD3864@crankycanuck.ca>
* 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