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

From korry.douglas
Subject Re: crypting prosrc in pg_proc
Date
Msg-id 46BB290F.4030807@enterprisedb.com
Whole thread Raw
In response to Re: crypting prosrc in pg_proc  (Hans-Juergen Schoenig <postgres@cybertec.at>)
Responses Re: crypting prosrc in pg_proc  (Hans-Juergen Schoenig <postgres@cybertec.at>)
List pgsql-hackers
> the idea is basically to hide codes - many companies want that and ask 
> for it again and again.
Hide code from who (or is that whom?)?  The PL compiler(s) will need to 
decrypt the code.  If a compiler can decrypt it, then anyone can decrypt 
it (because the compilers are open-source). 

And the problem is that any user that can run a function must be able to 
compile that function, and therefore, any user that can run a function 
must have the decryption key for that function.  So, I'm not sure you've 
secured the source code from any user that can run the function.

Of course, if your goal is to hide the code from someone snooping 
through the pg_proc relation (on disk), then encryption will certainly 
help (provided the key is properly protected).

Note: I think source-code encryption is a useful idea, it just seems 
tricky to implement in an open environment.
   -- Korry




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: crypting prosrc in pg_proc
Next
From: Decibel!
Date:
Subject: Re: HOT patch, missing things