Re: Misleading headline?
Indeed. The headline brought back memories of the days when I was contracting for a very large telco in the mid 1990s. All of a sudden every Windows 95 machine in their offices (which occupied five buildings) started crashing, all at the same time, once an hour. Some frantic Ethernet sniffing traced the problem to a malformed packet that triggered a bug in the 3C509 NIC driver on those machined, which in turn sparked a frantic network-wide driver update that should have been performed months earlier.
Interestingly, some of the old Unix SVr4 mini's in the server room also proved susceptible to the "ping of death" as we had dubbed it by then. Fixing that was much more difficult.
But the fecal matter really hit the rotating blades when we located the source of the malformed packets: one of the server admins on the night shift had installed an Open Source monitor application that was intended to detect, and alert the operators of, a server going down. It did so by sending the offending packet to the systems to be monitored, but said operator had failed to limit that to a handful of servers and instead just pinged the entire network.
I don't recall having seen much of him after that.
That's what the headline reminded me of. But that's not what this problem is really about.