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=0.6 required=5.0 tests=BAYES_00,TO_NO_BRKTS_FROM_MSSP autolearn=no 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: 109fba,582dff0b3f065a52 X-Google-Attributes: gid109fba,public X-Google-Thread: 1014db,582dff0b3f065a52 X-Google-Attributes: gid1014db,public X-Google-Thread: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-08-22 07:48:11 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!feed.textport.net!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.lang.functional From: Ted Dennison References: <3B6555ED.9B0B0420@sneakemail.com> <87n15lxzzv.fsf@deneb.enyo.de> <3B672322.B5EA1B66@home.com> <4a885870.0108112341.7ce02ac0@posting.google.com> <3B834E5D.B0D26AB1@adaworks.com> <9lvsic$bet9s$1@ID-9852.news.dfncis.de> <9m0193$grs$1@bird.wu-wien.ac.at> <9m08tm$bsbo3$1@ID-9852.news.dfncis.de> Subject: Re: How Ada could have prevented the Red Code distributed denial of service attack. Message-ID: X-Abuse-Info: When contacting newsranger.com regarding abuse please X-Abuse-Info: forward the entire news article including headers or X-Abuse-Info: else we will not be able to process your request X-Complaints-To: abuse@newsranger.com NNTP-Posting-Date: Wed, 22 Aug 2001 10:47:51 EDT Organization: http://www.newsranger.com Date: Wed, 22 Aug 2001 14:47:51 GMT Xref: archiver1.google.com comp.lang.ada:12236 comp.lang.c:76121 comp.lang.c++:84830 comp.lang.functional:7624 Date: 2001-08-22T14:47:51+00:00 List-Id: In article <9m08tm$bsbo3$1@ID-9852.news.dfncis.de>, Joachim Durchholz says... > >Markus Mottl wrote: >> In comp.lang.functional Joachim Durchholz wrote: >> > Could you share a reference to a report? >> >> Here is a somewhat longer treatment of the case: >> >> http://www.jerrypournelle.com/reports/jerryp/Yorktown.html >> >> In short: a divide-by-zero in a database caused a Windows NT server to >> crash, paralyzing the whole computer network on the cruiser Yorktown >> for more than two hours. >> >> As usual, official reports (i.e. by the Navy itself) that indicate >> shortcomings of their weapon technology do not circulate for too long >> for obvious reasons (but maybe they are just hidden well enough). > >Hmm. Looks as if NT wasn't really responsible, the thing was still under >test. :-) You clearly don't know much about the Navy to say this. You don't debug Navy engine controllers by putting them on a 1$ billion Cruiser with a proud captain and a full compliment of crew and having them steam around a bit to see what happens. Having a failure so bad that a ship has to be towed is *the* nightmare scenario in the naval engine controller biz. Its a public humiliation for the captain, and you can trust that heads *will* roll over it. Even after that, the captain is probably *never* going to trust that company's engine controllers again. If he one day gets into the procurement side, that could be disasterous for them. Any engine controller should have been completely debugged *years* before it ever touched a ship. The fact that there were still simple bugs at this point is a *scathing* inditment of something. We can argue over what that thing is, but there is no argument that is was a big deal. --- T.E.D. homepage - http://www.telepath.com/dennison/Ted/TED.html home email - mailto:dennison@telepath.com