I've not played around much with the Tcl Plugin, so I don't have a lot of specific information to impart. However, when working with the Tcl Plugin, keep in mind that your Tclet is running in a restricted enviroment. Specifically, it's running in a specialized "safe interpreter," that has all of the "unsafe" commands inaccessible by default. Unsafe commands include any command that could interact with the file system (such as
file,
glob,
cd,
pwd, etc.) or with the I/O channels (such as
open,
close,
socket,
fconfigure, etc.). This is intentional, to prevent untrusted Tclets from cause malicious or accidental damage or security leaks.
The interpreter included with the Plugin has support for a command called
policy, which can request less stringent security policies. For example, the "home" security policy is by default configured to allow a socket connection back to the same host that served the Tclet, as well as limited persistent storage on the client system.
Actual editing and administration of Tclet security policies is an area I never explored. But you can find out more information about the Tcl Plugin and configuring security policies from
You might also want to check the Tcl'ers Wiki (
starting with the page "Tcl/Tk Tclet Plugin,"
for more information. - Ken Jones, President, ken@avia-training.com
Avia Training and Consulting,
866-TCL-HELP (866-825-4357) US Toll free
415-643-8692 Voice
415-643-8697 Fax