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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,25d5234e7b6ca361 X-Google-Attributes: gid103376,public X-Google-Thread: fdb77,5f529c91be2ac930 X-Google-Attributes: gidfdb77,public X-Google-Thread: 1108a1,59ec73856b699922 X-Google-Attributes: gid1108a1,public X-Google-ArrivalTime: 2003-04-16 13:51:48 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!nntp.theplanet.net!inewsm1.nntp.theplanet.net!zen.net.uk!lon1-news.nildram.net!195.149.20.147.MISMATCH!mercury.nildram.co.uk!not-for-mail Message-ID: Date: Wed, 16 Apr 2003 21:36:47 +0100 From: Tom Welsh Reply-To: Tom Welsh Sender: Tom Welsh Newsgroups: comp.lang.java.advocacy,comp.object,comp.lang.ada Subject: Re: Ada versus language-X and "getting real work done" (was): 64 bit addressing and OOP References: <3E4E8F8C.9C096985@adaworks.com> <9fa75d42.0302250710.5549baaf@posting.google.com> <3E5C7033.BD5DC462@adaworks.com> <9fa75d42.0302260618.7506cba7@posting.google.com> <3E5CF5C6.84822F57@adaworks.com> <1046299823.547481@master.nyc.kbcfp.com> <1quq5v0sb922r76rbpmcs2pe19dr4i5a2r@4ax.com> <3E68C3CF.D4414313@agricoreunited.com> MIME-Version: 1.0 X-Newsreader: Turnpike Integrated Version 5.01 U NNTP-Posting-Host: 213.208.100.157 X-Trace: 1050526307 mercury.nildram.net 45172 213.208.100.157 Xref: archiver1.google.com comp.lang.java.advocacy:62271 comp.object:61198 comp.lang.ada:36211 Date: 2003-04-16T21:36:47+01:00 List-Id: In article <3E68C3CF.D4414313@agricoreunited.com>, Grant Wagner writes > >So, let's consider your C program. It receives input it is not expecting, the >stack buffer overflows and something happens (perhaps the software issues an >error) and the device restarts. No communication has taken place. > >Now let's consider a Java program. It receives input it is not expecting, there >is no buffer overflow, however the data is rejected as being invalid. No >communication has taken place. > >Your choice of language has made little difference. The fact that the C >programmed device had to restart is irrelevant to the argument that the device >could not communicate with another device, because both devices were talking to >each other using a different dialect to begin with. > Yeah, little difference except for the C program's buffer overflow which allows an attacker to modify its code and, in the worst case, take over the whole machine. -- Tom Welsh