1995-10-10 - Re: java security concerns

Header Data

From: m5@dev.tivoli.com (Mike McNally)
To: perry@piermont.com
Message Hash: cc4a53ca879c8cf86e29609ceb89ae5dce5b8e698a4d1e6a235adb388a4c0877
Message ID: <9510101301.AA28597@alpha>
Reply To: <Pine.SUN.3.90.951010002834.2770A-100000@dfw.net>
UTC Datetime: 1995-10-10 13:02:10 UTC
Raw Date: Tue, 10 Oct 95 06:02:10 PDT

Raw message

From: m5@dev.tivoli.com (Mike McNally)
Date: Tue, 10 Oct 95 06:02:10 PDT
To: perry@piermont.com
Subject: Re: java security concerns
In-Reply-To: <Pine.SUN.3.90.951010002834.2770A-100000@dfw.net>
Message-ID: <9510101301.AA28597@alpha>
MIME-Version: 1.0
Content-Type: text/plain



Perry E. Metzger writes:
 > To (perhaps over)simplify my point, the Java interpreter cannot be
 > stripped of all i/o capabilities and still remain useful. 

?!?  What if all I give you is a couple of Java classes that write to
a frame buffer, and that frame buffer is the screen (or your 24-pin
dot matrix printer or whatever)?

 > I can
 > physically remove all the "dangerous" calls from a Postscript
 > interpreter and still have it be useful.

I don't see the difference.  An interpreter is an interpreter.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Nobody's going to listen to you if you just | Mike McNally (m5@tivoli.com) |
| stand there and flap your arms like a fish. | Tivoli Systems, Austin TX    |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




Thread