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

Στις 27/7/2010 22:37, ο/η Ahmad έγραψε:
> 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

ActiveState's Tcl Development Kit (TDK)?

George

Ahmad 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?

TclApp which is in ActiveState's TDK.


-- 
+------------------------------------------------------------------------+
| Gerald W. Lester, President, KNG Consulting LLC                        |
| Email: Gerald.Lester@kng-consulting.net                                |
+------------------------------------------------------------------------+

On Jul 27, 2:01=A0pm, "Gerald W. Lester" <Gerald.Les...@KnG-
Consulting.net> wrote:
> Ahmad 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?
>
> TclApp which is in ActiveState's TDK.

You can encrypt object code? Didn't know that.

tom.rmadilo wrote:
> On Jul 27, 2:01 pm, "Gerald W. Lester" <Gerald.Les...@KnG-
> Consulting.net> wrote:
>> Ahmad 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?
>> TclApp which is in ActiveState's TDK.
> 
> You can encrypt object code? Didn't know that.

Sorry should have said TclCompiler -- by encrypt I assume he meant compile 
it so it can't be seen.

Of course, he might also like to deliver it as a single executable -- which 
would be TclApp (it can compile as during the wrap).

-- 
+------------------------------------------------------------------------+
| Gerald W. Lester, President, KNG Consulting LLC                        |
| Email: Gerald.Lester@kng-consulting.net                                |
+------------------------------------------------------------------------+

On 27 July, 22:14, "tom.rmadilo" <tom.rmad...@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.

=93Encrypt=94 is probably too strong. =93Obfuscate=94 is more accurate, sin=
ce
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.

On Jul 27, 4:07=A0pm, "Donal K. Fellows"
<donal.k.fell...@manchester.ac.uk> wrote:
> On 27 July, 22:14, "tom.rmadilo" <tom.rmad...@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.
>
> =93Encrypt=94 is probably too strong. =93Obfuscate=94 is more accurate, s=
ince
> 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

> 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

Ahmad wrote:
> On Jul 27, 4:07 pm, "Donal K. Fellows"
> <donal.k.fell...@manchester.ac.uk> wrote:
>> On 27 July, 22:14, "tom.rmadilo" <tom.rmad...@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.
>> =93Encrypt=94 is probably too strong. =93Obfuscate=94 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.
>=20
> Thanks all,
>=20
> Actually, what I meant is to keep the end-user unable to see the
> contents of my tcl files.
>=20
> 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?


--=20
+------------------------------------------------------------------------=
+
| Gerald W. Lester, President, KNG Consulting LLC                        =
|
| Email: Gerald.Lester@kng-consulting.net                                =
|
+------------------------------------------------------------------------=
+

On Jul 27, 3:37=A0pm, Ahmad <ahmad.abdulgh...@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

I tried freeWrap, and it seems to be excellent and easy to use.

One problem I have is that I'm not using normal TCL (tclsh), I'm using
CAD tool specifc tclsh having some built in custom API's for this
tool.

Hence, I need to make this script executable with something like: #!/
path/to/the/tool/bin/tool_tclsh

It seems that freeWrap converts the script blindly to be executable by
normal tclsh (available in $path).

Can I get around this somehow?

Thanks,
Ahmad


On Jul 28, 5:12=A0pm, DTM <gone2cani...@gmail.com> wrote:
> On Jul 27, 3:37=A0pm, Ahmad <ahmad.abdulgh...@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: =A0http://freewrap.sourceforge.net/
>
> Dennis

I tried freeWrap, and it seems to be excellent and easy to use.

One problem I have is that I'm not using normal TCL (tclsh), I'm using
CAD tool specifc tclsh having some built in custom API's for this
tool.

Hence, I need to make this script executable with something like: #!/
path/to/the/tool/bin/tool_tclsh

It seems that freeWrap converts the script blindly to be executable by
normal tclsh (available in $path).

Can I get around this somehow?

Thanks,
Ahmad


On Jul 28, 5:12=A0pm, DTM <gone2cani...@gmail.com> wrote:
> On Jul 27, 3:37=A0pm, Ahmad <ahmad.abdulgh...@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: =A0http://freewrap.sourceforge.net/
>
> Dennis

Dnia 28.07.2010 Ahmad <ahmad.abdulghany@gmail.com> napisa�/a:

> Actually, what I meant is to keep the end-user unable to see the
> contents of my tcl files.

There is an obfuscator called Frink: http://catless.ncl.ac.uk/Programs/Frink/

But it seems to be abandoned, as it works only up to TCL 8.4.x
-- 
Zbigniew