| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Justis Lincoln Mackaoui <jmackaou(at)calpoly(dot)edu> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Clarity Bug for Schema Permissions, Potential Vulnerability? |
| Date: | 2020-05-06 13:13:59 |
| Message-ID: | CAKFQuwY4PU5bews3XK4czceVnkmFzwEXDvP9nDDCwkiQoFipLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tuesday, May 5, 2020, Justis Lincoln Mackaoui <jmackaou(at)calpoly(dot)edu>
wrote:
>
> My argument is that step #6, the granting of privileges on the table,
> should return an “ERROR: permission denied” because the “test_user” should
> not know at all about the objects contained within “test_schema”. This
> would prevent the confusing state of contradictory permissions and access-
>
Hiding object existence is not something PostgreSQL does. Anyone can view
pg_class. So this is strictly a usability concern. At first glance I
concur that there seems to be room for improvement here.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2020-05-06 13:37:54 | Re: Clarity Bug for Schema Permissions, Potential Vulnerability? |
| Previous Message | PG Bug reporting form | 2020-05-06 09:30:25 | BUG #16418: postgis23_96 dependency proj49 missing now pgdg94 default to disabled |