<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Omar Shahine's WebLog : Apple</title><link>http://blogs.msdn.com/omars/archive/tags/Apple/default.aspx</link><description>Tags: Apple</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Apple iTunes DRM hole</title><link>http://blogs.msdn.com/omars/archive/2005/03/23/400783.aspx</link><pubDate>Wed, 23 Mar 2005 12:46:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:400783</guid><dc:creator>omars</dc:creator><slash:comments>0</slash:comments><comments>http://blogs.msdn.com/omars/comments/400783.aspx</comments><wfw:commentRss>http://blogs.msdn.com/omars/commentrss.aspx?PostID=400783</wfw:commentRss><description>&lt;P&gt;It seems that &lt;A href="http://www.internet-nexus.com/2005_03_20_archive.htm#111154360877215462"&gt;Paul Thurrott is astonished&lt;/A&gt; that Apple would apply DRM to purchased music on the client (iTunes) rather than the server. Seems like a really bad design decision and a good way to open the door for &lt;A href="http://www.daeken.com/2005/03/21/project-statement-for-pymusique"&gt;two programmers to crack it&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;The statement from &lt;A href="http://www.daeken.com/2005/03/21/project-statement-for-pymusique"&gt;their blog&lt;/A&gt; is precious:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;&lt;!--StartFragment --&gt;"Our intent was not to circumvent copy protection, and if Apple did DRM on the server, &lt;STRONG&gt;we would leave it in place!&lt;/STRONG&gt; But applying DRM in an opensource project is not worth the time it would take to code it."&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;If memory serves me right, when Apple first released Software Auto Update back with Mac OS X they &lt;A href="http://www.securityfocus.com/archive/1/280964"&gt;did not cryptographically sign their updates&lt;/A&gt;, which of course opened them up for a man in the middle attack delivering malicious code to their customers. Nor did they use any form of HTTP authentication or certificate validation when downloading updates. I remember this because when we developed our software update for Microsoft Office X I was sort of astonished that they did not code sign their updates or use https. Well it was a matter of time before they had to &lt;A href="http://www.eweek.com/article2/0,1759,1598257,00.asp"&gt;fix it&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;I guess hindsight is 20/20 (that goes for everyone). But personally I'm not surprised.&lt;/P&gt;&lt;img width="0" height="0" src="http://www.shahine.com/omar/cptrk.ashx?id=d95c325e-59f1-411e-bea6-0572ab0b6b86"&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=400783" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/omars/archive/tags/Software/default.aspx">Software</category><category domain="http://blogs.msdn.com/omars/archive/tags/Apple/default.aspx">Apple</category></item></channel></rss>