On 22 Jan 2007 at 10:15, Ron Johnson wrote:
> On 01/22/07 09:55, Jan Muszynski wrote:
> > On 22 Jan 2007 at 16:10, Sim Zacks wrote:
> >
> >> How good is postgresql security? For example, If I have data
> >> that I do not anyone to see, including the programmer/dba, is
> >> it enough to change the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 09:55, Jan Muszynski wrote:
> On 22 Jan 2007 at 16:10, Sim Zacks wrote:
>
>> How good is postgresql security? For example, If I have data
>> that I do not anyone to see, including the programmer/dba, is
>> it enough to change the password
On 22 Jan 2007 at 16:10, Sim Zacks wrote:
> How good is postgresql security?
> For example, If I have data that I do not anyone to see, including the
> programmer/dba, is it enough
> to change the password to the only user?
> If they have access to the raw files is there a way for them to someho
On Mon, Jan 22, 2007 at 08:30:53AM -0600, Ron Johnson wrote:
> > The answer depends heavily on what the "programmer/dba" can do.
> >
> > Any superuser of the DB can see any data
> > Any user that can access the raw files can see any data
> > Any user that can poke into memory can see any data
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/22/07 08:22, Martijn van Oosterhout wrote:
> On Mon, Jan 22, 2007 at 04:10:15PM +0200, Sim Zacks wrote:
>> How good is postgresql security?
>
> Good, within limits.
>
>> For example, If I have data that I do not anyone to see, including the
>>
On Mon, Jan 22, 2007 at 04:10:15PM +0200, Sim Zacks wrote:
> How good is postgresql security?
Good, within limits.
> For example, If I have data that I do not anyone to see, including the
> programmer/dba, is it enough to change the password to the only user?
> If they have access to the raw fil
am Mon, dem 22.01.2007, um 16:10:15 +0200 mailte Sim Zacks folgendes:
> How good is postgresql security?
> For example, If I have data that I do not anyone to see, including the
> programmer/dba, is it enough to change the password to the only user?
> If they have access to the raw files is there
How good is postgresql security?
For example, If I have data that I do not anyone to see, including the programmer/dba, is it enough
to change the password to the only user?
If they have access to the raw files is there a way for them to somehow see the
data?
can they copy the files to another
On Tue, 11 May 2004, [EMAIL PROTECTED] wrote:
> hello,
>
> i'm very new to postgres and have a fundamental question.
> how do i make a pg-db most secure?
> i feel, that pg_user e.g. ist something very dangerous - isn't it? if
> someone hacks into a db, then he has lots of information at his/her
> i'm very new to postgres and have a fundamental question.
> how do i make a pg-db most secure?
> i feel, that pg_user e.g. ist something very dangerous - isn't it? if
> someone hacks into a db, then he has lots of information at his/her
> fingertips. is this so?
>
> what do i do to prevent my
hello,
i'm very new to postgres and have a fundamental question.
how do i make a pg-db most secure?
i feel, that pg_user e.g. ist something very dangerous - isn't it? if
someone hacks into a db, then he has lots of information at his/her
fingertips. is this so?
what do i do to prevent my db fro
On Tue, May 11, 2004 at 20:09:46 +0200,
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> i'm very new to postgres and have a fundamental question.
> how do i make a pg-db most secure?
> i feel, that pg_user e.g. ist something very dangerous - isn't it? if
> someone hacks into a db, then he ha
[EMAIL PROTECTED] (Konstantinos Agouros) writes:
> Since I must grant update/insert/delete access to this table to everybody
> that can use this application, how can I stop people from updating the data
> of the others.
Triggers that compare current_user to the userid column of the table,
perhaps
13 matches
Mail list logo
