| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | protecting prosrc (was Re: USAGE on schema allowed by default?) |
| Date: | 2002-12-02 17:50:03 |
| Message-ID: | 3DEB9D4B.7090607@joeconway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Tom Lane wrote:
> For example, something I've heard repeatedly is that people would like to
> hide the source code of their SQL or PLxxx functions from users who are
> nonetheless allowed to call those functions. A row-wise selective view of
> pg_proc can't fix that. In many cases it's less than clear which rows of
> which catalogs to hide anyway.
It wouldn't be terribly difficult to encrypt prosrc with 3des (or maybe aes)
using the owner's passwd from pg_shadow. We would need a new bool column in
pg_proc (proisencrypted?) and some logic in fmgr.c.
Is there sufficient interest to justify the effort?
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-12-02 17:51:59 | Re: PostgreSql on windows |
| Previous Message | Joe Conway | 2002-12-02 16:56:41 | Re: [GENERAL] One SQL to access two databases. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-12-02 18:09:46 | Re: 7.4 Wishlist |
| Previous Message | Joe Conway | 2002-12-02 17:28:22 | Re: ALTER TABLE schema SCHEMA TO new_schema? |