From: | Nikola Milutinovic <Nikola(dot)Milutinovic(at)ev(dot)co(dot)yu> |
---|---|
To: | Premsun Choltanwanich <Premsun(at)nsasia(dot)co(dot)th> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to secure PostgreSQL Data for distribute? |
Date: | 2005-08-18 05:57:59 |
Message-ID: | 43042367.7000308@ev.co.yu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Premsun Choltanwanich wrote:
> Dear All,
>
> I need to distribute my application that use PostgreSQL as
> database to my customer. But I still have some questions in my mind on
> database security. I understand that everybody who get my application
> database will be have a full control permission on my database in case
> that PostgreSQL already installed on their computer and they are an
> administrator on PostgreSQL. So that mean data, structure and any
> ideas contain in database will does not secure on this point. Is my
> understanding correct?
>
> What is the good way to make it all secure? Please advise.
If you want to keep your data/schema "secure", you have to keep it at
your own place and that is just the first step in making it "secure".
Espionage, and that is what basically bothers you, is a complex field of
enterprize and there is no "one size fits them all".
Your first step is keeping the DB at your site and letting your
customers connect to it. This may present a huge problem, but there is
no other way. No encryption would work, trust me.
Nix.
From | Date | Subject | |
---|---|---|---|
Next Message | WireSpot | 2005-08-18 07:03:38 | Weird performance hit |
Previous Message | Joseph Shraibman | 2005-08-18 04:47:55 | Re: [JDBC] pg_locks.transaction field type |