You are viewing a read-only archive of the Blogs.Harvard network. Learn more.

The Longest Now


From a sysadmin: the perils of reporting trouble (from MeFi)
Sunday January 13th 2013, 6:10 pm
Filed under: chain-gang,meta,null

As a former sysadmin at MIT, I was very curious about this case and eager for the facts to come out, and I guess they can, but not like this. Definitely not like this. I also had the job of chasing intruders out of a segment of MIT’s network (fairly light duty, actually), and having been there I will state the following publicly, because I am pissed off today. Seriously pissed off.

These over the top prosecution of nuisance intrusions makes sysadmins like me highly reluctant to initiate communication with the feds. The threat of criminal prosecution was enough to make Mr. Swartz back off from his actions. That’s why MIT and JSTOR backed off. Someone at DOJ decided to keep going, and he just made life harder for federal investigators in countless other cases, who will not be getting that first phone call from a sysadmin.

When an intruder is on my network, before I call the authorities, I want to know that the authorities will exercise judgement and prosecute accordingly. If he’s a criminal trying to use my resources for crimes, that’s one thing. If he’s a kid or a kook being a nuisance, then the authorities have a duty to exercise precisely enough muscle to scare him off my network and call it a day. If I have reason to think that the authorities will throw the book at a someone who is a mild nuisance, then I won’t make the phone call. I will investigate the intrusiion myself, kick him off myself, and keep my fucking mouth shut. These prosecutions are a waste of money, and today one of them became a waste of a life.

Comments Off on From a sysadmin: the perils of reporting trouble (from MeFi)







Bad Behavior has blocked 226 access attempts in the last 7 days.