| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Yuli Khodorkovskiy <yuli(dot)khodorkovskiy(at)crunchydata(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Kohei KaiGai <kaigai(at)heterodb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: add a MAC check for TRUNCATE |
| Date: | 2019-09-06 15:38:48 |
| Message-ID: | 3b8900c8-0b03-77f3-ac25-f6c0a27790d4@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/6/19 11:26 AM, Yuli Khodorkovskiy wrote:
> On Fri, Sep 6, 2019 at 10:40 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>> There are actual reasons why the 'DELETE' privilege is *not* the same as
>> 'TRUNCATE' in PostgreSQL and I'm really not convinced that we should
>> just be tossing that distinction out the window for users of SELinux. A
>> pretty obvious one is that DELETE triggers don't get fired for a
>> TRUNCATE command, but TRUNCATE also doesn't follow the same MVCC rules
>> that the rest of the system does.
>
> I do agree with you there should be a distinction between TRUNCATE and
> DELETE in the SELinux perms. I'll wait a few days for more discussion
> and send an updated patch.
+1 - I don't think there is any question about it.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yuli Khodorkovskiy | 2019-09-06 15:40:48 | Re: add a MAC check for TRUNCATE |
| Previous Message | Tom Lane | 2019-09-06 15:35:13 | Re: pgsql: Use data directory inode number, not port, to select SysV resour |