<?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>Insecure 3rd party software updaters</title><link>http://blogs.msdn.com/michael_howard/archive/2008/07/29/insecure-3rd-party-software-updaters.aspx</link><description>Gotta love Robert's sarcasm .. but he's right.</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Insecure 3rd party software updaters</title><link>http://blogs.msdn.com/michael_howard/archive/2008/07/29/insecure-3rd-party-software-updaters.aspx#8791404</link><pubDate>Wed, 30 Jul 2008 14:04:37 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8791404</guid><dc:creator>Marc</dc:creator><description>&lt;p&gt;And you should blame Microsoft to not open auto-updates to other products than Microsoft ones.&lt;/p&gt;
&lt;p&gt;Why isn't Winzip (I do not speak about competing products like OpenOffice) allowed to use a secure and robust update mechanism instead of using a home made one ?&lt;/p&gt;
&lt;p&gt;Responsibility is not an answer; we are used to click on disclaimers when installing stuff, aren't we. One more disclaimer to accept an update from an &amp;quot;untrusted&amp;quot; (read non MS) source wouldn't be a problem.&lt;/p&gt;</description></item><item><title>re: Insecure 3rd party software updaters</title><link>http://blogs.msdn.com/michael_howard/archive/2008/07/29/insecure-3rd-party-software-updaters.aspx#8793097</link><pubDate>Thu, 31 Jul 2008 12:36:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8793097</guid><dc:creator>Marc</dc:creator><description>&lt;p&gt;And you should blame Microsoft to not open auto-updates to other products than Microsoft ones.&lt;/p&gt;
&lt;p&gt;Why isn't Winzip (I do not speak about competing products like OpenOffice) allowed to use a secure and robust update mechanism instead of using a home made one ?&lt;/p&gt;
&lt;p&gt;Responsibility is not an answer; we are used to click on disclaimers when installing stuff, aren't we. One more disclaimer to accept an update from an &amp;quot;untrusted&amp;quot; (read non MS) source wouldn't be a problem.&lt;/p&gt;</description></item><item><title>re: Insecure 3rd party software updaters</title><link>http://blogs.msdn.com/michael_howard/archive/2008/07/29/insecure-3rd-party-software-updaters.aspx#8845017</link><pubDate>Sat, 09 Aug 2008 16:46:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8845017</guid><dc:creator>securology</dc:creator><description>&lt;p&gt;Hmm. &amp;nbsp;Robert may be correct, but digital signatures by themselves do not make a secure update mechanism, unless there is a time-bound sensitivity associated with the signatures (and it would have to be a very finite amount of time at that). &amp;nbsp;Read more &amp;lt;a href=&amp;quot;&lt;a rel="nofollow" target="_new" href="http://securology.blogspot.com/2008/08/package-managers.html&amp;quot;&amp;gt;here&amp;lt;/a&amp;gt;"&gt;http://securology.blogspot.com/2008/08/package-managers.html&amp;quot;&amp;gt;here&amp;lt;/a&amp;gt;&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>