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,caa8ecf96e8cf189 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Trusting GNAT for security software Date: 1998/03/01 Message-ID: #1/1 X-Deja-AN: 329889889 References: <34F421F6.3A5FFF59@towson.edu> <34F5A906.1704@gsfc.nasa.gov> <34F68913.2FF865DA@cl.cam.ac.uk> <6d67j5$474$1@news.nyu.edu> <34F9444D.D2F588@cl.cam.ac.uk> <1998Mar1.142220.1@eisner> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 888808371 21841 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-03-01T00:00:00+00:00 List-Id: Larry said <> Actually here, operating in paranoid mode, you are ahead with GNAT, since, assuming you are using the commercial version of the product, you get it directly from the vendor, with no intervening distributors. Yes, it is possible that the public versions could be compromised, although I think it is more likely that would happen through an accident, than through design -- but one cannot imagine a paranoid security-concious project using unsupported freeware of unknown provenance, can one??? <> Surely you have not been dazzled into believing that because something is written in a standardized language, it is automatically portable! There are many legitimate implementation dependencies in almost all languages. It is actually very unusual for a large project to be 100% portable from one compiler to another without any changes of any kind at all -- not impossible, but most certainly unusual. Probably the most secure way of distributing security type products is to deliver the binary, together with the corresponding source. That way the customer can, if they like, repeat the entire certification process, or at least that part of the procedures that are related to the code itself, as opposed to the procedures used to generate the code. The danger of depending on source distribution for a high security product without any reference binary, is that you do not have a 100% guarantee that you have correctly compiled the product and got a version that corresponds to the one that has been certififed. FOr exampled in a nasty case, the compiler might have a previously undetected bug that causes it to generate bad code on the 29th of March, due to the date routine making a wild store.