from wired (here) Apple has announced that it has sold 60 million apps for the iPhone since its launch a month ago, that is a staggering 2 million a day and one of the reasons I proposed that the iPhone would introduce a mobile malware tipping point (here), what I didn’t realize at the time was that Apple had implemented a remote kill switch, which Steve Jobs himself confirmed with the WSJ (here).
Although I can understand the potential to do evil here I am far less concerned with Apple abusing their remote kill capabilities, like the US federal government would, and think it is a great idea they can reach out and kill a nefarious application – that is, of course, it till it is mine and it isn’t malicious just kind of subversive and anti-Apple…
While it’s good to know that a malicious application can be immediately yanked from all iPhones at the press of a button, it’s a little worrying, too. Given the level of secrecy inside Apple, we have a picture in our heads of some kind of virtual Guantanamo Bay inside One Infinite Loop, where bad applications are kept locked up indefinitely and tortured to find their secrets.




[...] Apple Implements Remote App Kill Switch for the iPhone « Amrit Williams Blog (tags: kill switch iphone apple) Posted in Suggested Blog Reading | var idcomments_acct=’90b2fde2bc0dbc10822f063f54ad16cc’; var idcomments_post_id=’318′; var idcomments_post_time=’2008-08-12 13:00:45′; var idcomments_post_author=’Andrew Hay’; var idcomments_post_title=’links+for+2008-08-12+%5Bdelicious.com%5D’; var idcomments_post_url=’http://www.andrewhay.ca/archives/318′; var commentScriptWrapper = document.createElement(“SCRIPT”); commentScriptWrapper.type = “text/javascript”; commentScriptWrapper.src = “http://www.intensedebate.com/js/wordpressTemplateCommentWrapper2.php?acct=”+idcomments_acct+”&postid=”+idcomments_post_id+”&title=”+escape(idcomments_post_title)+”&url=”+idcomments_post_url+”&posttime=”+idcomments_post_time+”&postauthor=”+idcomments_post_author; document.getElementsByTagName(“HEAD”)[0].appendChild(commentScriptWrapper); [...]