Re: Securing Postgres

From: Richard Huxton <dev(at)archonet(dot)com>
To: L van der Walt <mailing(at)lani(dot)co(dot)za>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Securing Postgres
Date: 2005-10-05 14:59:11
Message-ID: 4343EA3F.5030502@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

L van der Walt wrote:
> The big problem is that the administrators works for the client and not
> for me. I don't want the client to reverse engineer my database.
> There might be other applications on the server so the administrators do
> require root access.
>
> About the raw database files, I can use encryption to protect the data.

Well, if it's your client's machine, then they any competent
administrator will be able to work around anything you do. They set the
ground-rules you work in - you could be running inside a virtual machine
and never know.

If your database design is so advanced that you can't chance it falling
into the hands of others then you'll need to keep a separate machine and
lock it down yourself.

Are your clients really so dishonest that they'd break into the database
and take the necessary steps to hide their tracks too?

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-10-05 14:59:20 Re: selfmade datatype in C and server-crash
Previous Message Lincoln Yeoh 2005-10-05 14:52:36 Re: Securing Postgres