From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Andre Labuschagne <technical(at)eduadmin(dot)com> |
Cc: | "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Permissions |
Date: | 2016-09-20 20:48:13 |
Message-ID: | CAKFQuwbTsRokrLm=3juWFcc+YBR8Ue98ymwDV4SNHdZbvRfmSA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Tue, Sep 20, 2016 at 1:36 PM, Andre Labuschagne <technical(at)eduadmin(dot)com>
wrote:
>
> Sorry about the top posting. Still learning here.
>
> Hi David
>
> I am not making myself clear. Let us try another angle. We are concerned
> about security breaches and database theft within and outside the
> organisation. Assuming a rogue employee gets their hands on a full backup
> of one of the databases and they did not have the details of the only role
> that is listed as having privileges would this employee be able to download
> PG set it up on his or computer, provide a superuser password and then have
> full access to the database? Is there a way to prevent this access?
>
>
No. Not knowing the name of the only super user might be inconvenient but
its only security by obscurity. If they have unencrypted physical data
files
they have the potential see all of the data contained therein. They don't
even need passwords since they can just setup pg_hba.conf for trust access.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Debra Cerda | 2016-09-20 20:50:27 | Re: Permissions |
Previous Message | Andre Labuschagne | 2016-09-20 20:36:23 | Re: Permissions |