From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | korry <korry(at)starband(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_hba.conf alternative |
Date: | 2006-02-09 18:08:28 |
Message-ID: | 43EB851C.5010306@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
korry wrote:
>>>I was suggesting that pg_hba.conf could be stored in the same encrypting
>>>filesystem.
>>>
>>>
>>Then how can it be changed? What if you need to allow access from, say,
>>another user or another network? Oh, the admins have to change it ...
>>
>>
>
>Not all admins are equal... the admin that takes care of the database would
>obviously have the decrypt password for the encrypting filesystem. That
>admin (but not other admins) can change the pg_hba.conf file.
>
>
>
>
Why would you not simply set this up on a seperate machine to which only
the trusted admins had access? Most data centers I am familiar with use
single purpose machines anyway. If someone is trusted as root on your
box they can screw you no matter what you do. Pretending otherwise is
just folly.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2006-02-09 18:12:58 | Re: Upcoming re-releases |
Previous Message | Thomas Hallgren | 2006-02-09 17:54:07 | Re: User Defined Types in Java |