From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jwm(at)plain(dot)co(dot)nz |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re[2]: Restricting queries by the presence of a WHERE clause |
Date: | 2000-06-29 01:44:30 |
Message-ID: | 17976.962243070@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
John Morton <jwm(at)plain(dot)co(dot)nz> writes:
>> webclient <---> proxy <---> Postgres
> Minuses:
> - Another machine to buy
> - Root on the proxy is as bad as root was on the secure server, so..
> - The simple hack will need thorough security auditing
> - It's yet another machine to secure.
> - It's yet another point of failure.
What?? Who said anything about another machine? I was just
thinking another daemon process on the database server machine.
> What I'm really asking is is there any way of doing this with just
> triggers or rules, and if not, can a function be written to examine the
> where clause (or whatever it's called in the parse tree) and select
> triggers be hacked into the database?
No. If there were, what makes you think that it'd be easier to
security-audit it than a standalone proxy?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Charles Tassell | 2000-06-29 01:44:37 | Re: Interface Question |
Previous Message | Richard Harvey Chapman | 2000-06-29 01:14:25 | pg_atoi() |