| From: | "Gregory Williamson" <Gregory(dot)Williamson(at)digitalglobe(dot)com> |
|---|---|
| To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com>, <glynastill(at)yahoo(dot)co(dot)uk> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, "David Fetter" <david(at)fetter(dot)org>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, "Jonathan Bond-Caron" <jbondc(at)openmv(dot)com>, "Postgres General List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Obfuscated stored procedures (was Re: Oracle and Postgresql) |
| Date: | 2008-09-16 13:38:35 |
| Message-ID: | 8B319E5A30FF4A48BE7EEAAF609DB233021F338F@COMAIL01.digitalglobe.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-www |
Nice trick ... thanks!
> One big reason why nothing hasn't been done is that there is a decent
> 'low tech' obfuscation tactic already: remove select access from
> pg_proc to the user accounts in question and 'public'. This will
> essentially disable casual browsing of procedure code from user
> accounts.
<....>
> merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Bond-Caron | 2008-09-16 13:39:03 | Re: Obfuscated stored procedures (was Re: Oracle and Postgresql) |
| Previous Message | Gregory Stark | 2008-09-16 13:35:25 | Re: Index order |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Bond-Caron | 2008-09-16 13:39:03 | Re: Obfuscated stored procedures (was Re: Oracle and Postgresql) |
| Previous Message | Merlin Moncure | 2008-09-16 13:31:24 | Re: Obfuscated stored procedures (was Re: Oracle and Postgresql) |