<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- OPML generated by OPML Editor v11.0.6 on Thu, 05 Apr 2012 13:23:19 GMT -->
<opml version="2.0">
	<head>
		<title>Mac has a trojan botnet</title>
		<dateCreated>Thu, 05 Apr 2012 12:57:45 GMT</dateCreated>
		<dateModified>Thu, 05 Apr 2012 13:23:19 GMT</dateModified>
		<ownerName>Dave Winer</ownerName>
		<ownerEmail>dave.winer@gmail.com</ownerEmail>
		<expansionState>1</expansionState>
		<vertScrollState>1</vertScrollState>
		<windowTop>190</windowTop>
		<windowLeft>1127</windowLeft>
		<windowBottom>1181</windowBottom>
		<windowRight>2070</windowRight>
		</head>
	<body>
		<outline created="Thu, 05 Apr 2012 12:57:45 GMT" ctSaves="9" flPreview="false" id="2012.04.05.1749" server="xmlrpc://cms.scripting2.com:5337/RPC2" storySerialNum="1749" text="Mac has a trojan botnet" type="scripting2Post" url="http://scripting.com/stories/2012/04/05/macHasATrojanBotnet.html" username="davewiner" versionClient="0.44" versionServer="0.44" whenLastSave="Thu, 05 Apr 2012 13:23:20 GMT">
			<outline created="Thu, 05 Apr 2012 12:48:23 GMT" pgfnum="13466" text="I saw Microsoft making the mistake that Apple is making now. This isn't one of those mistakes where there's any &quot;maybe&quot; to it. It's an absolute 100 percent thing they're doing that they will regret. It will force their users to look for alternatives to the Mac unless they nip this one now."></outline>
			<outline created="Thu, 05 Apr 2012 12:49:25 GMT" pgfnum="13467" text="When there is an outbreak of a virus on the Mac, and they have a fix, that fix must go out immediately. If there is no fix, then resources must be devoted to finding it. As soon as there's a fix, the press must be notified. A press release must be issued, that clearly gives users a way of determinining &lt;i&gt;without installing any new software,&lt;/i&gt; whether their machine is infected. The communication must come from Apple, so there's no confusion among users and press. It would be smart to have a press event around security the same way they have press events to launch new products."></outline>
			<outline created="Thu, 05 Apr 2012 12:51:20 GMT" pgfnum="13468" text="&lt;img src=&quot;http://scripting.com/images/2012/04/05/indianGirl.gif&quot; width=&quot;77&quot; height=&quot;218&quot; border=&quot;0&quot; style=&quot;float: right; padding-left: 15px; padding-bottom: 5px; padding-top: 10px; padding-right: 15px;&quot; alt=&quot;A picture named indianGirl.gif&quot;&gt;They appear to have broken most of these practices in the response to &lt;a href=&quot;http://www.extremetech.com/computing/125019-mac-botnet-grows-to-600000-274-of-them-in-cupertino&quot;&gt;today's steamy infected mess&lt;/a&gt;. "></outline>
			<outline created="Thu, 05 Apr 2012 12:51:48 GMT" pgfnum="13469" text="There is now a fix, it's installed by the new system update that came out yesterday. But there has been no communication from Apple to users about this issue, or the press, and the only &lt;a href=&quot;http://www.f-secure.com/v-descs/trojan-downloader_osx_flashback_i.shtml&quot;&gt;test&lt;/a&gt; for infection has come from independent analysts. "></outline>
			<outline created="Thu, 05 Apr 2012 12:52:27 GMT" pgfnum="13470" text="Microsoft made the mistake of seeing themselves as merely a supplier of software, not a guarantor of good user experience. When Windows was inundated with malware, in the early-mid 2000's, users were left to fend for themselves. Apple was the beneficiary of this, as smart Windows users bailed on MS and switched to the Mac. Where the vendor boasted that they didn't have malware, as if there were some technical reason they didn't. There is so such technical reason. Macs are just as susceptible to malware as any other kind of computer. They just hadn't been targeted yet. Why it's taken so long is anyone's guess, but the honeymoon is now over. It's time for Apple to take this seriously. The way they do this is every bit as important as they way they operate their stores, do user testing, or industrial design."></outline>
			</outline>
		</body>
	</opml>
