| From: | bricklen <bricklen(at)gmail(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: leaky views, yet again |
| Date: | 2010-10-05 20:37:40 |
| Message-ID: | AANLkTik=vwx5EDU55fiP_XH6c=hiNM9jvA82mD4DzhcP@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 5, 2010 at 1:25 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Right now this is managed by query classes in our Java applications,
> but as we're moving to a variety of new and different technologies
> it's getting harder for the DBAs to ensure that nothing is leaking
> to inappropriate recipients. :-( I think we're going to need to
> move more of the enforcement to database views and/or security
> restrictions based on database roles.
Does Veil cover some of those needs?
http://veil.projects.postgresql.org/curdocs/index.html
I've never used it, but from what I recall hearing about it, it did
something similar (I thought).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2010-10-05 20:39:41 | Re: querying the version of libpq |
| Previous Message | Kevin Grittner | 2010-10-05 20:25:10 | Re: leaky views, yet again |