When you use the pp module in perl to create an exe from a script the actual script itself is compiled and cannot be viewed in a general text editor.

Since the app will be run over Citrix and our servers(in fact our whole end user environment) is completely locked down there will be no way to get at the details so not an issue

"When you use the pp module in perl to create an exe from a script the actual script itself is compiled and cannot be viewed in a general text editor."

Perhaps not an issue since you're running this via a Citrix interface but maybe you should take a look at the pp documentation again. At runtime the compressed executable extracts everything to a temporaty directory, where it can be viewed by whatever editor you like, this allows faster start up next time. Alternativly one could simply decompress to executable to obtain the goodies stored within. While source hiding techniques are available each have a work around. The faq over at http://par.perl.org is also worth reading.

I feel like I'm answering a whole new question here! :-)

You are of course correct concerning a bog standard use of pp on an end user system.

However, in my case I stand by the statement that the code is not viewable for the user. Because its a server side environment, the temp folder is created on the Citrix server in a temporary user profile (for each logged on user) which only the Citrix applications have access to. Users have no access rights to teh Citrix servers so cannot view these files. The temp folders are purged at logoff.

In any case, I've created a new OU in active directory to store the application groups that users will be allowed to add and remove themselves from. The admin account I'll be using to add/remove group access will ONLY have rights to the apps in that directory, so the security aspect is covered.