Lit. Buffer overruns 1684

so june 17th of some year ... the largest online service provider started having one of its internet connected service crash. for the next two months they had everybody they could think of come in to look at it ... but it continued to crash. so aug. 17, somebody came out and bought me a hamburger after work and while i ate it ... explained the symptoms. i then gave him a q&d work around patch that was applied later that night.

i made the rounds of the usual vendors that sell stuff that involves tcp-ip and-or connecting to the internet ... suggesting that maybe they do something to address the problem; nobody was interested.

almost exactly a year later a similar symptom hit a service provider in manhatten (it may have possibly even been aug. 17th of the following year) and all of a sudden it was in the press ... and now you saw the usual players telling the press about how fast they were addressing the problem.

now that particular service provider (that made the press) ... i believe may be the same one that was recently in the press with the domain name hijacking problem.

some recent domain name hijacking refs:

some random past posts mentioning domain name hijacking

--