Re: crypting prosrc in pg_proc - Mailing list pgsql-hackers

From Hans-Juergen Schoenig
Subject Re: crypting prosrc in pg_proc
Date
Msg-id 682976E7-1F8C-48EB-8F13-309763563894@cybertec.at
Whole thread Raw
In response to Re: crypting prosrc in pg_proc  ("korry.douglas" <korry.douglas@enterprisedb.com>)
Responses Re: crypting prosrc in pg_proc  (Andrew Sullivan <ajs@crankycanuck.ca>)
List 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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: change name of redirect_stderr?
Next
From: Decibel!
Date:
Subject: Re: crypting prosrc in pg_proc