| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp> |
| Subject: | Re: Updates of SE-PostgreSQL 8.4devel patches (r1268) |
| Date: | 2008-12-11 16:16:06 |
| Message-ID: | 200812111816.07853.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday 11 December 2008 17:09:25 Tom Lane wrote:
> I think there should be only *one* underlying column and that it should
> be manipulable by either SQL commands or selinux. Otherwise you're
> making a lie of the primary argument for having the SQL feature at all.
Well, an SQL-manipulated row security column will probably have a content like
{joe=rw/bob,staff=r/bob}
An SELinux-aware row security column will probably have a content like
blah_t:foo_t:quux_t
And a Solaris TX-aware security column will probably have a content like
Classified
How can we stick all of these in the same column at the same time?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2008-12-11 16:20:57 | Re: COCOMO & Indians |
| Previous Message | Hannu Krosing | 2008-12-11 16:14:04 | Re: COCOMO & Indians |