North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
RE: NY times appears to have had a rough morning..
Actually they were hacked by a group calling themselves HFG. The correct website was restored several times only to be overwritten by the hacked version minutes later. The hacked page talked about cron jobs, I imagine they hacked one in to keep putting the hacked web page up. Looks like they finally gave up and took down the server to fix it. > -----Original Message----- > From: firstname.lastname@example.org [mailto:email@example.com]On Behalf Of > Phil Howard > Sent: Sunday, September 13, 1998 10:51 AM > To: firstname.lastname@example.org > Cc: email@example.com > Subject: Re: NY times appears to have had a rough morning.. > > > Richard Irving wrote: > > > Hrmm.. This sunday am I logged into www.nytimes.com, > > and got an unusual front page. Someone may want to take > > a look...... > > Looks like the classical underconfigured/overloaded server to me. > They were > probably running with not much spare capacity before, or didn't > configure the > correct number of listening processes (or enough RAM to handle them). > > Possibly a SYN attack. But on this date, more likely a demand "attack". > > This is not unusual when you consider the total capacity is ultimately > determined by the suits. > > FYI, I had no trouble pulling it from icreport.loc.gov. I got it in the > evening, which would have been the 2nd demand curve for the day. > So server > capacity there was enough to deliver it in that probably broader > hump. But > maybe the masses, who normally go checking news sites and > wouldn't recognize > a .gov site as even being an Internet thing, were clobbering places like > www.nytimes.com. Even www.cnn.com seemed kinda slow to me. > > -- > Phil Howard | firstname.lastname@example.org email@example.com > firstname.lastname@example.org > phil | email@example.com firstname.lastname@example.org > email@example.com > at | firstname.lastname@example.org email@example.com > firstname.lastname@example.org > ipal | email@example.com firstname.lastname@example.org > email@example.com > dot | firstname.lastname@example.org email@example.com > firstname.lastname@example.org > net | email@example.com firstname.lastname@example.org > email@example.com >