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
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,5882b8e137d950f8,start
X-Google-Attributes: gid103376,public
From: "Marc A. Criley" <marc.a.criley@lmco.com>
Subject: DII COE bars Ada -> Java compilation
Date: 2000/04/05
Message-ID: <38EB3482.971747E4@lmco.com>#1/1
X-Deja-AN: 607037692
Content-Transfer-Encoding: 7bit
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@news.vf.lmco.com
X-Trace: knight.vf.lmco.com 954937772 22990 166.17.131.243 (5 Apr 2000
 12:29:32 GMT)
Organization: Lockheed Martin M&DS
Mime-Version: 1.0
NNTP-Posting-Date: 5 Apr 2000 12:29:32 GMT
Newsgroups: comp.lang.ada
Date: 2000-04-05T12:29:32+00:00
List-Id: <comp.lang.ada>

To Ada to JBC compiler vendors:

Section 8.2.3 (Miscellaneous) of the Defense Information Infrastructure
Common Operating Environment (DII COE) Integration & Run-Time
Specification (I&RTS) v4.0 states that "Developers shall not use
compilers designed to convert code developed in other languages (e.g.,
Ada, C++) to create Java byte-codes. This restriction is important
because such compilers may inadvertently bypass intended Java security
features."

Is this a legitimate concern?  I can kinda see how it might be, since
for instance Java forbids things like uninitialized objects (though I
vaguely recall some kind of exception to that), which Ada permits.  I
suspect I could probably come up with some other potential problems if I
dug into it.

If the Ada to JBC compilers do not introduce the security risks that the
I&RTS warns about, some educating is clearly called for.

Marc A. Criley
Software Architect
Lockheed Martin M&DS
marc.a.criley@lmco.com