| From: | Hans-Juergen Schoenig <postgres(at)cybertec(dot)at> |
|---|---|
| To: | "korry(dot)douglas" <korry(dot)douglas(at)enterprisedb(dot)com> |
| Cc: | "Zdenek Kotala" <Zdenek(dot)Kotala(at)Sun(dot)COM>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: crypting prosrc in pg_proc |
| Date: | 2007-08-09 15:16:43 |
| Message-ID: | 682976E7-1F8C-48EB-8F13-309763563894@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> The basic problem is this: if you have to decrypt the code in order
> to give it to a compiler (PL/pgSQL, Java, Perl, ...) then there is
> a point in time where the source code is in plaintext form - it
> would be trivial to add an fprintf( stderr, "%s", plainTextForm )
> to the PL handler to steal the code.
>
> -- Korry
if somebody is allowed to recompile on the box GRANT and REVOKE are
all useful.
you did not get the point, i think.
we are shipping appliances - users can only use SQL; no compilers and
no SSH logins allowed ...
hans
--
Cybertec Geschwinde & Schönig GmbH
Gröhrmühlgasse 26, 2700 Wiener Neustadt
Tel: +43/1/205 10 35 / 340
www.postgresql.at, www.cybertec.at
| From | Date | Subject | |
|---|---|---|---|
| Next Message | korry.douglas | 2007-08-09 15:17:33 | Re: crypting prosrc in pg_proc |
| Previous Message | Andrew Dunstan | 2007-08-09 15:15:51 | change name of redirect_stderr? |