Microsoft rolled out an update to its Windows XP operating system to add support for WPA2, aka Wi-Fi Protected Access 2, the wireless security specification approved by the IEEE.<\/p>\n","protected":false},"excerpt":{"rendered":"
Microsoft said the patch also contains support for WPS\/IE (Wireless Provisioning Services Information Element), the protocol that handles the distribution of configuration and service information to a wireless client.<\/p>\n
The WPA2 spec, also known as 802.11i, was ratified in June 2004 to pave the way for improved security within wireless networks. It replaced the stopgap WPA (Wi-Fi Protected Access) protocol and offers a more advanced encryption technique called AES (Advanced Encryption Standard). By adding support for WPA2, Microsoft can now market Windows XP Service Pack 2 with full FIPS 140-2 (Federal Information Processing Standard — Publication 140-2) support.<\/p>\n
According to a knowledge base article, users that download the Windows XP patch will be able to view previously hidden SSIDs (Service Set Identifiers) in the “Choose a Wireless Network” dialog box. This functionality simplifies the users’ connection to public Wi-Fi networks that were not previously connected.<\/p>\n
The AES using the CCMP (Counter Mode-Cipher Block Chaining-Message Authentication Code Protocol) that provides data confidentiality, data-origin authentication and data integrity for wireless frames.<\/p>\n
The optional use of PMK (Pairwise Master Key) caching and opportunistic PMK caching, allowing faster access when a wireless client roams back to a wireless access point to which the client has already authenticated.<\/p>\n
http:\/\/www.eweek.com\/article2\/0,1759,1791515,00.asp?kc=EWRSS03119TX1K0000594<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-660","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/660","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=660"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/660\/revisions"}],"predecessor-version":[{"id":3147,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/660\/revisions\/3147"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=660"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=660"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=660"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}