- Jan 29, 2006
- 9,066 (2.07/day)
- My house.
|Processor||AMD Athlon 64 X2 4800+ Brisbane @ 2.8GHz (224x12.5, 1.425V)|
|Motherboard||Gigabyte sumthin-or-another, it's got an nForce 430|
|Cooling||Dual 120mm case fans front/rear, Arctic Cooling Freezer 64 Pro, Zalman VF-900 on GPU|
|Memory||2GB G.Skill DDR2 800|
|Video Card(s)||Sapphire X850XT @ 580/600|
|Storage||WD 160 GB SATA hard drive.|
|Display(s)||Hanns G 19" widescreen, 5ms response time, 1440x900|
|Case||Thermaltake Soprano (black with side window).|
|Audio Device(s)||Soundblaster Live! 24 bit (paired with X-530 speakers).|
|Power Supply||ThermalTake 430W TR2|
|Software||XP Home SP2, can't wait for Vista SP1.|
A simple blunder in an E-mail server's code recently caused the Department of Homeland Security to give itself a miniature DDoS attack. Here's the low-down on what happened: a reader of the DHS' daily Open Source Intelligence Report replied to the list address with a request for a change. The message quickly found itself E-mailed to all subscribers of the newsletters, which numbers in the thousands, for reasons unknown. Unfortunately, once those subscribers got the request, they also got the list of recipients. When the good subscribers tried to report this problem, the same problem happened to the server, and every subscriber quickly found themselves knee-deep in E-mails asking for an un-subscription. That's not the only E-mail passed around the DHS network, though. Subscribers also received requests to cease replying, urgent requests from the Department of Defense and DHS officials for recipients to "kindly stop now please," a "vote for me" political ad, job offers and updates on the local weather. All in all, the server sent, received, and otherwise handled 2.2 million E-mails over the course of an hour, causing a mini-DDoS. The problem is resolved now, and the DHS is ensuring that such a problem will never happen again.