From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Curious case of the unstoppable user |
Date: | 2011-03-29 20:12:52 |
Message-ID: | 4D923D44.2030906@pinpointresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/29/2011 11:44 AM, Thom Brown wrote:
> Hi all,
>
> I've just set up a test user, revoked all access from them to a
> database, then tried to connect to that database and it let me in.
> When I try it all from scratch, it works correctly.
>
> Here's the set running correctly:
>
> postgres=# CREATE DATABASE testdb;
> CREATE DATABASE
> postgres=# CREATE ROLE testrole;
> CREATE ROLE
> postgres=# REVOKE ALL ON DATABASE testdb FROM testrole CASCADE;
> REVOKE
> postgres=# \c testdb testrole
> FATAL: role "testrole" is not permitted to log in
> Previous connection kept
>
> But now if I try something similar with an existing user and existing
> database, it doesn't work:
>
> postgres=# REVOKE ALL ON DATABASE stuff FROM meow CASCADE;
> REVOKE
> postgres=# \c stuff meow
> You are now connected to database "stuff" as user "meow".
>
> So, I'm overlooking something. Could someone tell me what it is? I
> bet it's something obvious. I'm using 9.1dev if it's relevant.
>
> Thanks
>
Not sure, but is user "meow" either the owner of the database "stuff" or
member of a group that permits access to "stuff"?
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-03-29 20:14:51 | Re: Curious case of the unstoppable user |
Previous Message | Raymond O'Donnell | 2011-03-29 20:06:52 | Re: Curious case of the unstoppable user |