1995-08-04 - Java and Safe-TCL security (was Re: Java, Netscape, OpenDoc, and Babel)

Header Data

From: Phil Fraering <pgf@tyrell.net>
To: rjc@clark.net
Message Hash: 830615ba050d130d4608f9f64ea04cf71bb08b1ec65856e3a123985075a42be9
Message ID: <199508042243.AA08602@tyrell.net>
Reply To: <199508042152.RAA12471@clark.net>
UTC Datetime: 1995-08-04 22:48:23 UTC
Raw Date: Fri, 4 Aug 95 15:48:23 PDT

Raw message

From: Phil Fraering <pgf@tyrell.net>
Date: Fri, 4 Aug 95 15:48:23 PDT
To: rjc@clark.net
Subject: Java and Safe-TCL security (was Re: Java, Netscape, OpenDoc, and Babel)
In-Reply-To: <199508042152.RAA12471@clark.net>
Message-ID: <199508042243.AA08602@tyrell.net>
MIME-Version: 1.0
Content-Type: text/plain


   From: Ray Cromwell <rjc@clark.net>
   Date: Fri, 4 Aug 1995 17:52:24 -0400 (EDT)

     SafeTcl or Java? I wish SafeTcl was isolated into a separate library
   with compiled-in safety so I could embed it into my applications. As it is
   now, I have to just use normal Tcl and hack in the MakeInterpreterSafe()
   function which removes dangerous commands.

   -Ray

You mean the "dangerous" commands can't just be left out of the proper
place in the makefile or something?

Phil





Thread