From: | Hector Beyers <hqbeyers(at)gmail(dot)com> |
---|---|
To: | Peter Hunsberger <peter(dot)hunsberger(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Hiding data in postgresql |
Date: | 2010-05-24 20:24:27 |
Message-ID: | AANLkTilLFT6NMBy33S6sU3ksrH6o0Y4RdfAg9BegxAAO@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Dear Peter,
can you elaborate on what you mean by storing 'this' in the index. Are you
referring to the function that is applied over the data?
How would you be able to see the result with a dump?
Thanks, your ideas are really helping...
Regards
Hector
On Mon, May 24, 2010 at 9:30 PM, Peter Hunsberger <
peter(dot)hunsberger(at)gmail(dot)com> wrote:
> On Mon, May 24, 2010 at 2:16 PM, Hector Beyers <hqbeyers(at)gmail(dot)com> wrote:
> >
> > Hi guys,
> > does ANYONE have any tips on hiding data on a database server? This means
> > that data is stored in places that is not necessarily picked up in the
> > schema of the database. I am doing some research on databases and need
> some
> > direction.
> > Any help or direction will be highly appreciated.
>
> Let me guess: an attempt at security by obscurity?
>
> I suppose you could always create a couple of columns such that some
> function applied over them produced the real result (. You could even
> actually store this in an index, so although you could never see the
> result directly (except in a dump) queries to get at it might perform
> half reasonably.
>
> --
> Peter Hunsberger
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Hunsberger | 2010-05-24 20:29:27 | Re: Hiding data in postgresql |
Previous Message | Peter Hunsberger | 2010-05-24 20:23:38 | Re: Hiding data in postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Hunsberger | 2010-05-24 20:29:27 | Re: Hiding data in postgresql |
Previous Message | Peter Hunsberger | 2010-05-24 20:23:38 | Re: Hiding data in postgresql |