From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Evan Rempel <erempel(at)uvic(dot)ca> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: How to revoke privileged from PostgreSQL's superuser |
Date: | 2018-08-15 19:28:38 |
Message-ID: | 20180815192838.GA5005@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Wed, Aug 15, 2018 at 09:05:51AM -0700, Evan Rempel wrote:
> At the end of the day someone has full access and control and can do anything without auditing database statements.
>
> For instance, as the root user on the server, I can do:
>
> - shutdown the server database
> - copy the entire DB filespace to my workstation
> - change the workstation config for no logging/auditing
> - start the workstation Database
> - make all the changes I want at the workstation.
> - stop the workstation database
> - copy all of the files back to the server
> - start the server Database.
>
> no logging of any kind and all of the data would be suspect.
Well, that is an intersting attack, and I don't think it requires root
--- all it requires is access to the Postgres data directory. Frankly,
I don't know if there is a way to prevent the Postgres superuser from
silently disabling logging because the _data_ is fully under the control
of the Postgres superuser.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
From | Date | Subject | |
---|---|---|---|
Next Message | Evan Rempel | 2018-08-15 20:13:10 | Re: How to revoke privileged from PostgreSQL's superuser |
Previous Message | Evan Rempel | 2018-08-15 16:05:51 | Re: How to revoke privileged from PostgreSQL's superuser |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2018-08-15 19:29:43 | Re: Code of Conduct plan |
Previous Message | Stephen Frost | 2018-08-15 19:22:10 | Re: Code of Conduct plan |