From: | Petr Jelinek <pjmodos(at)pjmodos(dot)net> |
---|---|
To: | KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jan Urban'ski <wulczer(at)wulczer(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] DefaultACLs |
Date: | 2009-10-06 12:54:58 |
Message-ID: | 4ACB3E22.5050305@pjmodos.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
KaiGai Kohei napsal(a):
> I tried to check the default ACL behavior.
>
> It works for me fine, good, but ...
>
> postgres=> SELECT * INTO t3 FROM t1;
> SELECT
> postgres=> SELECT * FROM t3;
> a | b
> ---+-----
> 1 | aaa
> 2 | bbb
> (2 rows)
>
> postgres=> INSERT INTO t3 VALUES (3,'ccc');
> ERROR: permission denied for relation t3
>
> In this case, the new table t3 is created with the default ACL which does not
> allow to insert any values by the owner of the relation.
>
> SELECT INTO does not check ACL_INSERT on the newly created tables, because
> we had been able to assume the table owner always has privilege to insert
> values into the new table.
> So, OpenIntoRel() didn't check this obvious privilege.
>
> But the default ACL feature breaks this assumption. The table owner may not
> have privilege to insert values into new tables.
> So, it is necessary to put actual access controls on the OpenIntoRel().
>
That's strange behavior I agree. However I don't see how default ACLs
changed it in any way, owner could REVOKE his privileges before.
--
Regards
Petr Jelinek (PJMODOS)
From | Date | Subject | |
---|---|---|---|
Next Message | Petr Jelinek | 2009-10-06 13:03:25 | Re: [PATCH] DefaultACLs |
Previous Message | Magnus Hagander | 2009-10-06 12:09:10 | Re: Encoding issues in console and eventlog on win32 |