On Sat, 10 May 2003 15:30:43 +0200, paul@pjcj.net (Paul Johnson) wrote: >On Fri, May 09, 2003 at 01:41:01PM +0100, Mat Harris wrote: > >Top posting moved to the bottom. > >> On Thu, May 08, 2003 at 07:52:19 -0400, zentara wrote: >> > >> > So how can you write a perl script which can't be deparsed? >> > Real nice "fishing lesson".....thanks. >> >> you could just use perlcc which compiles it as a c prgoram. it is just as hard >> to decompile as any c binary > >That's fine provided you understand what perlcc is and what it isn't. >The docs state: > >| The code generated in this way is not guaranteed to work. The whole >| codegen suite (perlcc included) should be considered very experimental. >| Use for production purposes is strongly discouraged. > >If you can live with that, and the knowledge that perlcc is buggy, >incomplete, and is not currently being worked on, (or better yet, if you >want to change that) then use perlcc. Hello again everyone. After asking about this on http://perlmonks.org, I found out that setting the "taint mode" switch on the scripts, before they are compiled by shc, will prevent them from being deparsed by Pauls' method. Now the question is: can you turn off taint mode with another environmental variable?Thread Previous | Thread Next