Re: WIP: plpgsql source code obfuscation
| От | Gregory Stark | 
|---|---|
| Тема | Re: WIP: plpgsql source code obfuscation | 
| Дата | |
| Msg-id | 871w82q6u5.fsf@oxford.xeocode.com обсуждение исходный текст  | 
		
| Ответ на | Re: WIP: plpgsql source code obfuscation (Andrew Dunstan <andrew@dunslane.net>) | 
| Ответы | 
                	
            		Re: WIP: plpgsql source code obfuscation
            		
            		 | 
		
| Список | pgsql-patches | 
Someone along the way suggested doing this as a kind of "wrapper" PL language. So you would have a PL language like "obfuscate:plperl" which would obfuscate the source code on the way in. Then when you execute a function it would deobfuscate the source code and then just pass it to the normal plperl. In such a scheme I think you would put the key in an attribute of the language. Either in pg_lang or some configuration location which the obfuscate:plperl interpreter knows where to find. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning
В списке pgsql-patches по дате отправления: