Bernd Eidenschink wrote:
Well, the line above, if uncommented, creates a (big) file which holds all
procs sourced in after startup.
Is it a bad idea, maybe before use on the production system, to let AOLserver
create the file, byte compile the procs, adding "load libtbcload..." and
sourcing this f
> Is it a bad idea, maybe before use on the production system, to let
AOLserver
> create the file, byte compile the procs, adding "load libtbcload..." and
> sourcing this file instead of running through the process every time?
procomp/tbcload is designed for obfuscation, not speed. It will
not sp
> > #catch { set fh [open init_interp_code.tcl w] ; puts $fh $init ;
> > close $fh }
> >
> > in namespace.tcl, proc _ns_getinit.
> > Somebody ever tried this?
>
> What do you mean? What exactly are you trying to achieve?
Well, the line above, if uncommented, creates a (big) file which holds all
p
...
> Thinking about it I think it is reasonably secure, the only command that I
> don't know how to deal with so far is "info", as it is called with "info
> procs", "info body" (...) in "namespace.tcl" and I need the "info exists"
> part by myself.
You can override any command you want, o
Thanks for your answers, Jeff and Dossy.
> Just do 'rename unsafeCmd {}'. There is no need to do it at the C level.
Yes, I already rename some commands to "" / {} nirvana :-)
Thinking about it I think it is reasonably secure, the only command that I
don't know how to deal with so far is "info",
