[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Mon Aug 23 22:26:16 2004 -->
- <!--x-from-r13: owbea ng fppf.fjneguzber.rqh (Pwbea Rvggzre-Dbpur) -->
- <!--x-message-id: [email protected]-a-geek.com -->
- <!--x-reference: 04Aug23.143932-0400_edt.316090-[email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] OT: A funny one from Computerworld on XP SP2 -->
- <li><em>date</em>: Mon Aug 23 22:26:16 2004</li>
- <li><em>from</em>: bjorn at sccs.swarthmore.edu (Bjorn Dittmer-Roche)</li>
- <li><em>in-reply-to</em>: <<a href="msg00595.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00595.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] OT: A funny one from Computerworld on XP SP2</li>
>
>> <a rel="nofollow" href="http://www.computerworld.com/softwaretopics/os/story/0,10801,9">http://www.computerworld.com/softwaretopics/os/story/0,10801,9</a>
>> 5390,00.html
>
> Thanks. Now if I could just figure out when buffer overflows became the most
> popular DoS attack, or when they became a DoS attack at all for that matter,
> I'd be all set. Any denial of service caused by a buffer overflow is either
> due to a poorly written exploit or is a mere side effect. If we surmise that
> a buffer overflow is by definition a DoS attack, then EVERY attack is a DoS
> attack and the water is now completely mud choked. The article is pretty
> misleading, and it's overall theme is factually inaccurate from the
> beginning. A buffer overflow is nothing more than a vehicle for attack. It
> is my understanding that the MS solution misrepresented here works by simply
> killing the attacking process, not shutting down the entire system. This may
> be an exercise in semantics, but details are important when discussing
> technical matters. Based on their misguided ideas of how things work, I
> wouldn't pay these two "consultants" to clean my windows (pun intended) for
> fear of them painting them instead.
I think you are absolutely right. My reading of it is that they are
misusing the term buffer overflow. I think they are referring to
overflowing some internal network buffer when an attacker sends a ton of
data, so when the OS gets send more network data than it has buffers for
it shuts down. I would be interested in a clarification on this one if
anyone knows better. the link on the words "buffer overflow" give more or
less correct definition, though.
bjorn
PS why am I suddenly receiving all ALE messages twice?
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00609" href="msg00609.html">[ale] OT: A funny one from Computerworld on XP SP2</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
<li><strong><a name="00610" href="msg00610.html">[ale] OT: A funny one from Computerworld on XP SP2</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00595" href="msg00595.html">[ale] OT: A funny one from Computerworld on XP SP2</a></strong>
<ul><li><em>From:</em> jdr at xcorps.net (Jonathan Rickman)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00604.html">[ale] [semi OT] No CIFS data</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00606.html">[ale] OT: Goodbye Bellsouth, Hello Speedfactory!</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00595.html">[ale] OT: A funny one from Computerworld on XP SP2</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00609.html">[ale] OT: A funny one from Computerworld on XP SP2</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00605"><strong>Date</strong></a></li>
<li><a href="threads.html#00605"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>