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,LOTS_OF_MONEY 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: 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-01 14:11:39 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!sn-xit-01!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: "Mike Smith" 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: Wed, 1 Aug 2001 17:07:20 -0400 Organization: Posted via Supernews, http://www.supernews.com Message-ID: References: <3B6555ED.9B0B0420@sneakemail.com> <87n15lxzzv.fsf@deneb.enyo.de> <3B672322.B5EA1B66@home.com> <5ee5b646.0108010949.5abab7fe@posting.google.com> <%CX97.14134$ar1.47393@www.newsranger.com> X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-Complaints-To: newsabuse@supernews.com Xref: archiver1.google.com comp.lang.ada:10986 comp.lang.c:71397 comp.lang.c++:79161 comp.lang.functional:7105 Date: 2001-08-01T17:07:20-04:00 List-Id: "Ted Dennison" wrote in message news:L5Y97.14163$ar1.47661@www.newsranger.com... > > I found a mirror which folks like me behind facist firewalls may have an easier > time accessing. http://www.supportamerica.com/win_buff/win_buff_overflow.html . > If you don't understand the buffer overflow problem (which apparently, at least > Mike doesn't) Yes, I do. However, what I also understand is that buffer overflow problems are a *bug*, not a "feature", and they are a bug in the *application code*, not the language. Only improperly written C code can contain buffer overflow problems, and there is absolutely *no* excuse for finding them in C++ code, because the STL can be used to eliminate them completely. -- Mike Smith