From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5882b8e137d950f8 X-Google-Attributes: gid103376,public From: Robert Dewar Subject: Re: DII COE bars Ada -> Java compilation Date: 2000/04/08 Message-ID: <8cm9e5$9el$1@nnrp1.deja.com>#1/1 X-Deja-AN: 608166343 References: <38EB3482.971747E4@lmco.com> <8cfg7m$qbd$1@nnrp1.deja.com> <38EDE91D.C6A9EC19@ftw.rsc.raytheon.com> X-Http-Proxy: 1.0 x34.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Sat Apr 08 03:35:33 2000 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.61 [en] (OS/2; I) Date: 2000-04-08T00:00:00+00:00 List-Id: In article <38EDE91D.C6A9EC19@ftw.rsc.raytheon.com>, Wes Groleau wrote: > And in fact, one security report I read described a security > hole that could be exploited by a byte-code assembler but > which was prevented by a "correct" Java compiler. But that is the function of the byte code verifier. Obviously unverified code is risky no matter *what* the source. One certainly has far more faith in the verifier than in *any* compiler. Sent via Deja.com http://www.deja.com/ Before you buy.