{"id":17889,"date":"2013-09-25T10:34:09","date_gmt":"2013-09-25T17:34:09","guid":{"rendered":"http:\/\/www.intego.com\/mac-security-blog\/?p=17889"},"modified":"2016-10-06T12:23:24","modified_gmt":"2016-10-06T19:23:24","slug":"feds-admit-to-hacking-tor","status":"publish","type":"post","link":"https:\/\/www.intego.com\/mac-security-blog\/feds-admit-to-hacking-tor\/","title":{"rendered":"Feds Admit to Hacking Tor"},"content":{"rendered":"

\"Man<\/a><\/p>\n

Remember that shocking incident about a month ago, where the Feds were suspected of hacking Tor<\/a> and cutting off a huge chunk of the Tor “onion?” When reports about it surfaced, some people were like “Hey, this came from a government contractor’s IP,” and then we were like “Yeah, we can’t really be sure of that<\/a>.”\u00a0Well, here’s a wrinkle I totally didn’t see coming…<\/p>\n

With\u00a0all the difficulties in conclusively identifying the origin, we weren’t certain that this came from the government. There was only one way to know for sure, and it wouldn’t be easy to find out. So the Feds made it easy and admitted that it was their doing<\/a>; they took credit for hacking Tor.<\/p>\n

Oh. Okay, I can’t really argue with that evidence.<\/p>\n

The FBI told an Irish court<\/a> that it was the one creating the code, which they designed to surreptitiously capture an affected user’s MAC address and IP address.<\/p>\n

According to Gizmodo<\/a>:<\/p>\n

\n

The Tor hack was supposed to target associates of the Freedom Hosting’s operator Eric Eoin Marques who’s currently being detained in Dublin, Ireland for his involvement in a massive child pornography operation. Freedom Hosting has indeed been under suspicion of allowing kiddie porn on its servers for some time now, but the investigation took a turn for the technical when the Feds exploited a loophole in the version of Firefox that forms the basis for the Tor Browser Bundle.<\/p>\n<\/blockquote>\n

Regardless of anyone’s opinions of the rightness or appropriateness of these actions, it’s interesting in that it brings an end to a mystery that’s been floating around since at least 2007<\/a>. And now that the code is out in the open, the Feds will have to go back to the drawing board if they try to do something like this again.<\/p>\n

More than that, it brings up an interesting question about “perfect” security. This is something that has been coming up a lot lately: if security can be easily broken by an adversary who is sufficiently determined, is it worthwhile at all?<\/p>\n

The TouchID hack<\/a> is one good example, and many people are discussing whether encryption is still useful, given that the NSA has been tampering with encryption standards by inserting a backdoor<\/a> that makes it trivial for them to break in. It’s also been shown that Tor users can be identified by a sufficiently determined adversary<\/a>, given a few months’ worth of traffic.<\/p>\n

Generally speaking, I would rather have imperfect security<\/a> and be aware of its potential flaws so that I can take other steps to mitigate potential problems. For instance, Intego routinely recommends\u00a0using layered defenses<\/a>\u00a0to improve your overall security. Tor getting hacked serves as an important reminder that nothing is 100 percent effective on its own, and it’s important that we realize this in order to effectively identify and mitigate risks.<\/p>\n","protected":false},"excerpt":{"rendered":"

Remember that shocking incident about a month ago, where the Feds were suspected of hacking Tor and cutting off a huge chunk of the Tor “onion?” When reports about it surfaced, some people were like “Hey, this came from a government contractor’s IP,” and then we were like “Yeah, we can’t really be sure of […]<\/p>\n","protected":false},"author":6,"featured_media":18345,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[13,5],"tags":[553,63,569],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\n\n\t\n\t\n\t\n