{"id":1297,"date":"2004-03-05T00:00:00","date_gmt":"2004-03-05T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/03\/05\/microsoft-windows-xp-sp2-will-be-disruptive\/"},"modified":"2021-12-30T11:39:07","modified_gmt":"2021-12-30T11:39:07","slug":"microsoft-windows-xp-sp2-will-be-disruptive","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/03\/05\/microsoft-windows-xp-sp2-will-be-disruptive\/","title":{"rendered":"Microsoft: Windows XP SP2 Will be Disruptive"},"content":{"rendered":"<p>Worried that the full release of its Windows XP Service Pack 2 (SP2) will break and disrupt existing applications, Microsoft (Quote, Chart) has created an online training course for developers to explain the intricacies of the security-centric OS update.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The launch of a training course is an unusual move for the software giant, which has changed many Windows XP defaults to tighten security and to simplify the software update process.  The service pack, now in beta, will make significant changes to deal with increased network protection, memory protection, improved e-mail security and enhanced browsing security; but these changes will lead to major disruption unless developers tweak their applications, the company explained.<\/p>\n<p>In a detailed explanation, Microsoft made it clear that IT administrators and users must make specific changes to allow applications to open certain ports.  &#8220;Windows Firewall includes an explicit setting in the firewall to enable the automatic opening and closing of ports for RPC for each profile.<\/p>\n<p>More info: http:\/\/www.internetnews.com\/ent-news\/article.php\/3322381<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1297","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1297","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1297"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1297\/revisions"}],"predecessor-version":[{"id":3784,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1297\/revisions\/3784"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1297"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1297"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1297"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}