The rexxc program (supplied with ooRexx) can remove the ability of anyone from seeing the original source code. But be sure to save a copy of the original source as you can not get it back from the code produced by rexxc.
David Ashley On Tue, 2014-09-30 at 11:00 -0500, Bertram Moshier wrote: > Hi! > > > (I looked around for this topic using Google, but didn't find anything > before posting here. If there is a better search facility, please, > let me know.) > > > > I'm working on several programs for various people, but don't want to > share the source code. I'm wondering if there is a way to protect a > program you write from an user either reading and/or modifying the > code? If yes, great! Ah, what is it? If no, how can I submit this > as a feature request for a future release. Specifically, if it is a > new feature the requirements I see are: > > > > The programmer can set the ooRexx program file so the user can: > * Only read but can't make changes the ooRexx interpreter will > recognize. > * Neither read nor modify any program. > * Allow the end user to read and modify the program, but require > a new program name for the saved program. > * Allow the end user to read and save the original program. > > My thought on how to implement would be a new exe file / program to > create and maintain these program files. The rexx.exe, dll, etc would > need to know how to read the new binary files. NOTE: I don't look > at this as a compiler but closer to encryption of the ooRexx program. > > (As for US export, the encrypt / decrypt) could be an user-exit > supplied by the programmer. What would come with ooRexx is a simple > template that would do something similar to zip, which should be OK > for release worldwide.) > > Thank you, > > Bert. > > > > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-users mailing list > Oorexx-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Oorexx-users mailing list Oorexx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-users
