Tcl code encryption best practice -- Please help
in [TCL]
|
Prev: Parser tools : "expected start <= end for range"
Next: Help fix my code: Problem in making folder contents backup then delete it
From: Donal K. Fellows on 27 Jul 2010 19:07 On 27 July, 22:14, "tom.rmadilo" <tom.rmad...(a)gmail.com> wrote: > Gerald W. Lester wrote: > > Ahmad wrote: > > > What are the best practice in encrypting Tcl script? > > TclApp which is in ActiveState's TDK. > You can encrypt object code? Didn't know that. Encrypt is probably too strong. Obfuscate is more accurate, since the code has to become machine-executable at some point. The obfuscator is not invincible, not by a long stretch, but combine it with suitable packaging and users won't realize what they've got or pick it apart. For most users, a standard starpack is just as effectively protected because they don't see the source when they double-click on it. The extra complexity that the tclcompiler adds is definitely enough to keep out all but the ultra-determined, and that's Good Enough. Donal.
From: Ahmad on 27 Jul 2010 20:23 On Jul 27, 4:07 pm, "Donal K. Fellows" <donal.k.fell...(a)manchester.ac.uk> wrote: > On 27 July, 22:14, "tom.rmadilo" <tom.rmad...(a)gmail.com> wrote: > > > Gerald W. Lester wrote: > > > Ahmad wrote: > > > > What are the best practice in encrypting Tcl script? > > > TclApp which is in ActiveState's TDK. > > You can encrypt object code? Didn't know that. > > Encrypt is probably too strong. Obfuscate is more accurate, since > the code has to become machine-executable at some point. The > obfuscator is not invincible, not by a long stretch, but combine it > with suitable packaging and users won't realize what they've got or > pick it apart. For most users, a standard starpack is just as > effectively protected because they don't see the source when they > double-click on it. The extra complexity that the tclcompiler adds is > definitely enough to keep out all but the ultra-determined, and that's > Good Enough. > > Donal. Thanks all, Actually, what I meant is to keep the end-user unable to see the contents of my tcl files. I don't know if using a tool that convert tcl code into a binary executable (compiling it) can allow me to include it in other files as used to deal with normal tcl files. Thanks, Ahmad
From: Harald Oehlmann on 28 Jul 2010 03:59 > Actually, what I meant is to keep the end-user unable to see the > contents of my tcl files. David Zolli has presented LRIOBFC on EuroTCL conference which should do what you want: http://www.lr-i.com/LRIOBF.html Regards, Harald
From: Gerald W. Lester on 28 Jul 2010 09:50 Ahmad wrote: > On Jul 27, 4:07 pm, "Donal K. Fellows" > <donal.k.fell...(a)manchester.ac.uk> wrote: >> On 27 July, 22:14, "tom.rmadilo" <tom.rmad...(a)gmail.com> wrote: >> >>> Gerald W. Lester wrote: >>>> Ahmad wrote: >>>>> What are the best practice in encrypting Tcl script? >>>> TclApp which is in ActiveState's TDK. >>> You can encrypt object code? Didn't know that. >> Encrypt is probably too strong. Obfuscate is more accurate, since >> the code has to become machine-executable at some point. The >> obfuscator is not invincible, not by a long stretch, but combine it >> with suitable packaging and users won't realize what they've got or >> pick it apart. For most users, a standard starpack is just as >> effectively protected because they don't see the source when they >> double-click on it. The extra complexity that the tclcompiler adds is >> definitely enough to keep out all but the ultra-determined, and that's >> Good Enough. >> >> Donal. > > Thanks all, > > Actually, what I meant is to keep the end-user unable to see the > contents of my tcl files. > > I don't know if using a tool that convert tcl code into a binary > executable (compiling it) can allow me to include it in other files as > used to deal with normal tcl files. The short answer is yes if you use the TclCompiler -- from ActiveState. Have you looked at the TDK web pages? Have you downloaded the free trial copy and tried it? -- +------------------------------------------------------------------------+ | Gerald W. Lester, President, KNG Consulting LLC | | Email: Gerald.Lester(a)kng-consulting.net | +------------------------------------------------------------------------+
From: DTM on 28 Jul 2010 20:12
On Jul 27, 3:37 pm, Ahmad <ahmad.abdulgh...(a)gmail.com> wrote: > Hi, > > I have a tcl script that I need to ship to my customer encrypted as > it's some propitiatory contents that I don't need him to see. > > What are the best practice in encrypting Tcl script? > > Thanks, > Ahmad I believe that the freeWrap application can do what you want. FreeWrap can turn your TCL script into an executable binary with your source code encrypted. See the freeWrap home page at: http://freewrap.sourceforge.net/ Dennis |