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.1 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII X-Google-Thread: 107f24,582dff0b3f065a52 X-Google-Attributes: gid107f24,public X-Google-Thread: 1014db,582dff0b3f065a52 X-Google-Attributes: gid1014db,public X-Google-Thread: 109fba,582dff0b3f065a52 X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-02 10:49:22 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!psinet-eu-nl!psiuk-p4!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.lang.functional Subject: Re: How Ada could have prevented the Red Code distributed denial of service attack. Date: Thu, 2 Aug 2001 13:37:39 -0400 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9kc355$ri0$1@nh.pace.co.uk> References: <3B687EDF.9359F3FC@mediaone.net> NNTP-Posting-Host: 136.170.200.133 X-Trace: nh.pace.co.uk 996773861 28224 136.170.200.133 (2 Aug 2001 17:37:41 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 2 Aug 2001 17:37:41 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:11110 comp.lang.c:71696 comp.lang.c++:79402 comp.lang.functional:7205 Date: 2001-08-02T17:37:41+00:00 List-Id: Can you point to a *single* post in this thread where *anyone* claimed that writing programs in Ada guaranteed bug-free code? And you've got it bass-ackwards - they took the range checks *out* because their analysis indicated the values could *never* exceed valid ranges - so long as you were in an Arianne 4 flight envelope. Without the range checks, the math triggered a hardware overflow that the FDA decisions indicated *must* be a sensor failure because it *couldn't* happen in an Arianne 4 flight envelope. Hence, shut down the channel and switch to the other side. The software worked as it was designed to work - doing *exactly* what the programmers wanted it to do - it just wasn't the right thing for Arianne 5. MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/ "Goran Larsson" wrote in message news:GHGA3t.Izq@approve.se... > In article , > Preben Randhol wrote: > > > Perhaps read it again. > > Why? > > The report clearly shows that you can have problematic software in > any language. It was also ironic that it was a compiler generated > range check on a value (that was not going to be used) that was the > event that started the destructive chain of events. The management > decision that any exception had to be due to hardware error (and > warranted a shutdown) was _perhaps_ influenced by the belief that > writing code in Ada resulted in bug free programs. :-) > > -- > G�ran Larsson Senior Systems Analyst hoh AT approve DOT se