Timeline for Restrict access for Windows administrator in PostgreSQL
Current License: CC BY-SA 3.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| May 8, 2013 at 12:15 | answer | added | Craig Ringer | timeline score: 4 | |
| May 8, 2013 at 10:31 | comment | added | Remus Rusanu | You can't hide anything from the local administrator. | |
| May 8, 2013 at 10:02 | comment | added | user1822 | Correct, just like the answer for SQL Server was. Aaron's (accepted answer) sums it up pretty well: "If you don't trust someone, don't give them Windows Administrator rights, period." | |
| May 8, 2013 at 9:57 | comment | added | Colin 't Hart | So the answer is no. The Windows administrator on the machine that Postgres (or any software) is installed on can do anything to the installed software and thereby get access. | |
| May 8, 2013 at 9:54 | comment | added | user1822 | There is no direct link between Windows users and Postgres users (there is no "Windows Authentication"). So simply don't tell your Windows administrator the Postgres DBA passwort (of course the Windows administrator can always edit pg_hba.conf so that isn't much protection) | |
| May 8, 2013 at 9:54 | review | First posts | |||
| May 8, 2013 at 13:09 | |||||
| May 8, 2013 at 9:53 | history | edited | user1822 | CC BY-SA 3.0 |
added 5 characters in body
|
| May 8, 2013 at 9:36 | history | asked | user2006840 | CC BY-SA 3.0 |