| From: | oleg yusim <olegyusim(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Shared system resources |
| Date: | 2015-12-23 00:03:32 |
| Message-ID: | CAKd4e_F9SkhXhyzt-Lw0miTzfHxkQ3YfOu7fM-dX0Zyy89FKQw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
John,
Absolutely. But we are not talking about that type of data leakage here. We
are talking about potential situation when user, who doesn't have access to
database, but has (or gained) access to the Linux box DB is installed one
and gets his hands on data, database processes stored in memory (memory
would be a common resource here).
Thanks,
Oleg
On Tue, Dec 22, 2015 at 5:28 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 12/22/2015 2:52 PM, oleg yusim wrote:
>
>
> *The DBMS must prevent unauthorized and unintended information transfer
> via shared system resources.*
>
>
>
> you realize the database *itself* is a shared system resource.... and of
> and by itself has no idea about unauthorized/unintended information
> transfer, eg, any user with the proper credentials to connect to the
> database can query any tables those credentials are allowed to?
>
> --
> john r pierce, recycling bits in santa cruz
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-12-23 02:36:44 | Re: Test disk reliability (or HGST HTS721010A9E630 surprisingly reliable) |
| Previous Message | John R Pierce | 2015-12-22 23:28:26 | Re: Shared system resources |