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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 107f24,582dff0b3f065a52 X-Google-Attributes: gid107f24,public X-Google-Thread: 1014db,582dff0b3f065a52 X-Google-Attributes: gid1014db,public X-Google-Thread: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-Thread: 109fba,582dff0b3f065a52 X-Google-Attributes: gid109fba,public X-Google-ArrivalTime: 2001-08-02 20:11:27 PST Path: archiver1.google.com!newsfeed.google.com!postnews1.google.com!not-for-mail From: mjsilva@jps.net (Mike Silva) 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: 2 Aug 2001 20:11:27 -0700 Organization: http://groups.google.com/ Message-ID: <5267be60.0108021911.7d8fe4@posting.google.com> References: <9k9if8$rn3$1@elf.eng.bsdi.com> <3B687EDF.9359F3FC@mediaone.net> NNTP-Posting-Host: 209.239.210.9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 996808287 7378 127.0.0.1 (3 Aug 2001 03:11:27 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 3 Aug 2001 03:11:27 GMT Xref: archiver1.google.com comp.lang.ada:11161 comp.lang.c:71800 comp.lang.c++:79528 comp.lang.functional:7235 Date: 2001-08-03T03:11:27+00:00 List-Id: "Tor Rustad" wrote in message news:... > "Preben Randhol" wrote in message > > On Thu, 2 Aug 2001 05:21:25 GMT, Goran Larsson wrote: > > > In article <3B687EDF.9359F3FC@mediaone.net>, > > > Ed Falis wrote: > > > > > >> Read the report. > > > > > > I have. Your point is? > > > > Perhaps read it again. > > Looks like I need to read the report again aswell. :-) > > IIRC, the problem was related to excetion handling of a hardware fault...not > exactly a Ada programming bug, but more a technical design bug...? Very briefly, they had proven to their satisfaction that the offending variable could never go out of range (of a 16 bit integer) on the Ariane 4, and any unhandled exception, such as the one that occurred when it *did* go out of range on the -5, was presumed to be due to a hardware fault, leading to shutdown of the unit. Since both units received the same "impossible" value, due to the -5s different trajectory, both shut down... Not only wasn't it a programming bug, I wouldn't even call it a design bug, since hardware failure would have been the correct presumption based on the Ariane 4 trajectory data. It was an untested, unjustified re-use bug. Mike