This content has been marked as final. Show 3 replies
What's the best current method for hiding or securing componentized code, e.g. Include files?
I'd like to be able to reference an evolving library of code (subroutines, etc...) in a client app, without giving away IP. But, of course, Include files are plain text.
Is there a reasonable way to encrypt an include such that it's decrypted by the (hidden) script at runtime?
Difficulty: the files must be local to the server (no reaching through URLs), and reasonably easy for use to revise or edit.