From: | "Igor Georgiev" <gory(at)alphasoft-bg(dot)com> |
---|---|
To: | |
Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Security question : Database access control |
Date: | 2002-10-22 16:45:07 |
Message-ID: | 015401c279ea$615d2e40$0b0546c0@alpha.bg |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
> Next your going to ask what will stop root from stopping your
> PostgreSQL, compiling a second copy with authentication disabled and
> using your data directory as it's source :)
He he i'm enough paranoic :))
> If you want to prevent root from accomplishing these things, you're
> going to have to look to your kernel for help. The kernel must prevent
> root from changing users, starting / stopping applications, or touching
> certain filesystems.
>
> PostgreSQL will let you put a password on the data. But that only works
> if they actually try to use PostgreSQL to get at the data.
use PostgreSQL to get at the data - Yeah this will be enough
i want just only REVOKE CONNECT PRIVILEGES on database
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Boes | 2002-10-22 17:42:44 | Drop and reload table to clear corruption? |
Previous Message | Igor Georgiev | 2002-10-22 16:34:57 | Re: Security question : Database access control |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-10-22 16:46:55 | Re: pg_dump and large files - is this a problem? |
Previous Message | Igor Georgiev | 2002-10-22 16:34:57 | Re: Security question : Database access control |