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 somebody can blow up ur home with C4, but this don't stop you from
locking ur door !?!
On Fri, 25 Oct 2002, Igor Georgiev wrote:
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 somebody can blow up ur home with C4, but this don't stop you
On Tue, 2002-10-22 at 12:12, Igor Georgiev wrote:
edit *pg_hba.conf *
# Allow any user on the local system to connect to any
# database under any username, but only via an IP connection:
host all 127.0.0.1 255.255.255.255trust
Is there any way to prevent superuser to acces the
database ?
I mean something like "GRANT /
REVOKE CONNECT" MECHANISM
I have no idea how to prevent root from access data
in one of this ways :
root @ linux:~#su
- postgres
postgres @
linux:/usr/local/pgsql/bin$pg_dump
or
edit
edit *pg_hba.conf *
# Allow any user on the
local system to connect to any
# database under any
username, but only via an IP connection:
host
all
127.0.0.1 255.255.255.255
trust
# The same, over
Unix-socket connections:
local
all
trust
what about reading pg_hba.conf
On Tue, 22 Oct 2002, Igor Georgiev wrote:
edit *pg_hba.conf *
# Allow any user on the local system to connect to any
# database under any username, but only via an IP connection:
host all 127.0.0.1 255.255.255.255trust
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