Word: servers
(lookup in dictionary)
(lookup stats)
Dates: during 2000-2009
Sort By: most recent first
(reverse)
John, whose business attire consists of a buzzcut and hoodie, takes in requests on the phone, matching up his 65 strippers and 15 drivers to his shows. Three computers surround him. One is for the company website’s server, one for booking shows, and one for MapQuesting locations as far away as the border between New York and Canada...
...clear that the operator of this computer wasn’t actually after information about the computer society’s illustrious alums; rather, he’d found a hole in the code behind the web page, a way to run programs on HCS’s server. He made quick work of defacing our home page, replacing it with a spartan battle flag (still visible online at http://hcs.harvard.edu/hackedindex.shtml) announcing that “Unknown Core Own3d Harvard.” “Brazil rlz,” the attackers noted...
Attacks like this aren’t uncommon. HCS has suffered a handful over the past year, the web server for the Electrical Engineering and Computer Science (EECS) department has been similarly attacked, and the people.fas server, which holds student home pages, is at the very least vulnerable, if anyone is running poorly written code on it (and, surely, someone is). To be fair, these attacks aren’t terribly dangerous—barring deeper security problems, they can’t really do much more damage than messing up a few web sites, and clever configuration can even...
...first few attempts at tracking the four down were not successful, but I did get to talk to some other hackers—one, a Moroccan who went by the name “St00Rm,” astutely sized up the situation “ur server is haxoris3d.” He wasn’t our attacker though—he looks down on page defacements and only hacks servers to steal some of their bandwidth in order to host his own web sites. Of our institution, he had only one question: “harvard...
...unapologetic, perfectly reasonable. Unknown Core was, he asserted, helping HCS: they had found a vulnerability in our server and had pointed it out to us while doing only a very small amount of easily repairable damage. Wasn’t this better, he asked, than had some other more malicious hacker come along and tried to use the security breach to more nefarious ends? He wasn’t interested in my suggestion that he might have emailed us instead. He didn’t seem bothered by my claim he was just pointing out holes in Swiss Cheese anyway...