How to protect tcl source code?
Einstein30000
Kit (ActiveState), but the compiler always crashes?
Today I've read "blowfish encryption" at http://wiki.tcl.tk/3698 . Any
ideas how to encrypt an windows executable with blowfish??
Please help me!
Gerald W. Lester
Get the ActiveState TDK
--
+--------------------------------+---------------------------------------+
| Gerald W. Lester |
|"The man who fights for his ideals is the man who is alive." - Cervantes|
+------------------------------------------------------------------------+
Einstein30000
> Einstein30000 wrote:
> > I'd like to protect my source code. I've tried "ProComp" from Tcl Dev
> > Kit (ActiveState), but the compiler always crashes?
>
> > ideas how to encrypt an windows executable with blowfish??
>
> Get the ActiveState TDK
>
> --
> +--------------------------------+---------------------------------------+
> | Gerald W. Lester |
> |"The man who fights for his ideals is the man who is alive." - Cervantes|
> +------------------------------------------------------------------------+
I already got it, but it doesn't work how i like it ;)
The compiled excutables got many errors!
Gerald W. Lester
What kind of errors?
Are you saying it gives errors when you compile -- if so what ones?
Or are you saying you get errors when you run it that you do not get if you
run the uncompiled code -- again if so what ones?
Einstein30000
right, i get error that i dont get when i run the uncompiled code.
Gerald W. Lester
> right, i get error that i dont get when i run the uncompiled code.
What is the error????
Einstein30000
He isn't able to load some dll libraries.
Gerald W. Lester
> On 1 Mrz., 19:12, "Gerald W. Lester" <Gerald.Les...@cox.net> wrote:
>> Einstein30000 wrote:
>>> right, i get error that i dont get when i run the uncompiled code.
>> What is the error????
>
That has nothing to do with compiling the code -- it has to do with wrapping
the code.
To prove this to yourself, wrap the uncompiled code and try to run it.
If you still have problems, please post exactly what message you are
getting, what extension, and what DLLs it uses.
Einstein30000
I wrapped the uncompiled code using prowrap.exe from TDK, when i try
to use procomp.exe, the procomp crashes!??
Gerald W. Lester
procomp compiles .tcl into .tbc
What I said was to wrap the uncompiled code and run the resultant exe -- do
that.
Einstein30000
Yes, i've done that. I've tried to use procomp, after it doesn't work
is used prowrap with the tcl-file, and the resultant program isn't
able to load some dll's form Img 1.3 and the ini.dll.
Gerald W. Lester
Hmm, just noted that you say prowrap and procomp -- those are in some rather
old versions of the ActiveState TDK. Please upgrade and see if that solves
your problem.
Einstein30000
I use the files from version 1.4.1, its the newest version as far as i
know.
David Gravereaux
> Einstein30000 wrote:
[snip]
>> Yes, i've done that. I've tried to use procomp, after it doesn't work
>> is used prowrap with the tcl-file, and the resultant program isn't
>> able to load some dll's form Img 1.3 and the ini.dll.
>>
>
> Hmm, just noted that you say prowrap and procomp -- those are in some
> rather old versions of the ActiveState TDK. Please upgrade and see if
> that solves your problem.
>
Wait a sec here! ProWrap (all vintage 1.1 - 1.5) *requires* that the all the
extensions used be contained statically inside the wrapper shell (ie.
bigwish-???.exe). The [load] command in the resultant wrapped exe will not work
for security reasons!
Whereas, TclApp, the wrapper based on metakit does not have that restriction. It
does require that all the extensions used support Stubs and have a .tap file that
describes the package (as produced by TclApp -scan).
IOW, please use TclApp contained in the ActiveState TDK rather than the old
ProWrap to support the inclusion of external packages not contained in the base
wrapper executable.
--
Know what I pray for? The strength to change what I can, the inability to
accept what I can't and the incapacity to tell the difference. -- Calvin
Jeff Hobbs
> I'd like to protect my source code. I've tried "ProComp" from Tcl Dev
> Kit (ActiveState), but the compiler always crashes?
procomp hasn't been the name of the TDK compiler for quite a while.
If you are using the latest release, it is called tclcompiler(.exe).
Furthermore, if you are trying to wrap, the application is named
tclapp(.exe) and has an option to automatically protect source code as
you wrap (no interim step necessary). This certainly does work with
the Img library, as I've used it myself.
Please try again with TDK 3.2 from:
http://www.activestate.com/Products/Tcl_Dev_Kit/
Jeff
David Gravereaux
> I use the files from version 1.4.1, its the newest version as far as i
> know.
>
That was built in August 2000. I should know, I was the one @ Scriptics that
compiled it (or maybe Brent or Micheal, but I know I kicked off numerous dailies)
That is *not* the ActiveState TDK. It is the TclPro toolset made by
AjubaSolutions (Scriptics).
You are missing out on six years of development work by using that old toolset.
http://www.activestate.com/products/tcl_dev_kit/
http://aspn.activestate.com/ASPN/docs/Tcl_Dev_Kit/3.2/TclApp.html
--
"Dad buried in landslide! Jubilant throngs fill streets! Stunned father
inconsolable - demands recount!" -- Calvin
Einstein30000
Donal K. Fellows
> Oh, sorry, i thought Tcl Dev Kit == ProTcl?!?
Six or so years ago, yes. But not now. :-)
If you need single-file packaging, experiment with building starkits.
If you need anti-tamper stuff, buy the TDK (or Komodo) from
ActiveState (and also do that if you need both anti-tamper and
packaging) since they're the primary vendors of that sort of thing.
What there isn't is lots of Open Source support for anti-tamper stuff;
it's sort-of philosophically anti-open, so we mostly don't want to
work on that sort of thing. :-D
Donal.
Dennis LaBelle
Take a look at freeWrap at http://freewrap.sourceforge.net/
It creates executable files out of TCL scripts and automatically encrypts
them.
Dennis LaBelle