<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Sunday update on Microsoft Security Advisory 935964 </title><link>http://blogs.technet.com/msrc/archive/2007/04/22/sunday-update-on-microsoft-security-advisory-935964.aspx</link><description>Hello everyone, This is Christopher Budd. I wanted to take a moment and provide a brief update on the situation from our work over the weekend. As of tonight, the situation remains unchanged. Our teams are continuing to work on developing and testing</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Friday update on Microsoft Security Advisory 935964 </title><link>http://blogs.technet.com/msrc/archive/2007/04/22/sunday-update-on-microsoft-security-advisory-935964.aspx#834796</link><pubDate>Sat, 28 Apr 2007 01:10:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:834796</guid><dc:creator>The Microsoft Security Response Center (MSRC)</dc:creator><description>&lt;p&gt;Hello everyone, This is Christopher Budd. We’ve not seen any new developments in the DNS situation but&lt;/p&gt;
</description></item></channel></rss>