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.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM, FREEMAIL_REPLYTO,REPLYTO_WITHOUT_TO_CC 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: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-Thread: 1014db,582dff0b3f065a52 X-Google-Attributes: gid1014db,public X-Google-ArrivalTime: 2001-08-09 23:48:04 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!130.133.1.3!fu-berlin.de!uni-berlin.de!212.102.229.162!not-for-mail From: "Joachim Durchholz" 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: Fri, 10 Aug 2001 08:47:54 +0200 Message-ID: <9l0032$6rq6p$1@ID-9852.news.dfncis.de> References: <9kpo9r$415@augusta.math.psu.edu> <5drpk9.l0e.ln@10.0.0.2> <9krhd2$6po@augusta.math.psu.edu> <9kubta$h4p$1@nh.pace.co.uk> <9kup40$6pomr$1@ID-9852.news.dfncis.de> Reply-To: "Joachim Durchholz" NNTP-Posting-Host: 212.102.229.162 X-Trace: fu-berlin.de 997426083 7203033 212.102.229.162 (16 [9852]) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Xref: archiver1.google.com comp.lang.ada:11742 comp.lang.c:73345 comp.lang.c++:81478 comp.lang.functional:7459 Date: 2001-08-10T08:47:54+02:00 List-Id: Larry Kilgallen wrote: > "Joachim Durchholz" writes: > > Marin David Condic wrote: > >> Failure of software is 100% due to mistakes made by the author. :-) > > > > Wrong. A sizable fraction is due to misunderstandings between author and > > customer (or whoever writes the specifications), and it's not always the > > author who's responsible for them. > > It was a mistake by the author to accept an ambiguous specification. Or an inconsistent one, for that matter. However, specifications are never complete. If the customer were able to write a complete specification, he wouldn't need a programmer after all. And it's the missing parts that give rise to the usual problems. > If the specification is unambigous but not what the customer wanted, > that is not a failure of the software. Technically not, but it creates exactly the same sort of hassles as a programmer mistake. Regards, Joachim -- This is not an official statement from my employer.