<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to upgrade and patch for wpa2 KRACK? in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/How-to-upgrade-and-patch-for-wpa2-KRACK/m-p/4604#M132</link>
    <description>Hello Jeronimo, Community, &lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; SZ 3.5.1 and 3.4.2 (latest native releases) install a .noarch.patch file.&amp;nbsp; If you have Zones&lt;BR /&gt;under 3.5.1 or 3.4.2 for versions 3.2.1 or 3.1.2, you install .ksp files.&amp;nbsp; Please see the descriptions&lt;BR /&gt;on the SZ firmware download pages. They have the exact filenames and extentions for your&lt;BR /&gt;reference.&amp;nbsp; SZ-100 and vSZ-E controllers need to be upgraded to 3.4.2 or 3.5.1 presently.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/software/1481-smartzone-3-5-1-mr1-patch1-software-release-wpa2-krack-patch" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/software/1481-smartzone-3-5-1-mr1-patch1-software-release-wpa2-krack-patch"&gt;https://support.ruckuswireless.com/software/1481-smartzone-3-5-1-mr1-patch1-software-release-wpa2-kr...&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/software/1482-smartzone-3-4-2-mr2-patch2-software-release-wpa2-krack-patch" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/software/1482-smartzone-3-4-2-mr2-patch2-software-release-wpa2-krack-patch"&gt;https://support.ruckuswireless.com/software/1482-smartzone-3-4-2-mr2-patch2-software-release-wpa2-kr...&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Management has decided to create .noarch.patch files to directly upgrade systems that are&lt;BR /&gt;running 3.2.1 and 3.1.2 in native mode (such as SZ-100/vSZ-E)&amp;nbsp;and ZD 9.7.2, and these should &lt;BR /&gt;come before the end of November.&lt;BR /&gt;&lt;BR /&gt;Please follow current status information on our Ruckus KRACK Support Resource Center page.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/krack-ruckus-wireless-support-resource-center" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/krack-ruckus-wireless-support-resource-center"&gt;https://support.ruckuswireless.com/krack-ruckus-wireless-support-resource-center&lt;/A&gt;</description>
    <pubDate>Wed, 01 Nov 2017 16:14:18 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2017-11-01T16:14:18Z</dc:date>
    <item>
      <title>How to upgrade and patch for wpa2 KRACK?</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/How-to-upgrade-and-patch-for-wpa2-KRACK/m-p/4603#M131</link>
      <description>Hi.&lt;BR /&gt;&lt;BR /&gt;I have seen RN for KRACK patch.&lt;BR /&gt;&lt;BR /&gt;There is written as 1) APPLY AP PATCH 2) APPLY KSP FIX 3) APPLY AP CLI Scripts.&lt;BR /&gt;&lt;BR /&gt;I can't find a file about 2) KSP FIX.&lt;BR /&gt;&lt;BR /&gt;Where is the KSP file.?&lt;BR /&gt;&lt;BR /&gt;And Must I apply the KSP file on SZ?&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards.</description>
      <pubDate>Wed, 01 Nov 2017 10:38:43 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/How-to-upgrade-and-patch-for-wpa2-KRACK/m-p/4603#M131</guid>
      <dc:creator>hyosang_choi</dc:creator>
      <dc:date>2017-11-01T10:38:43Z</dc:date>
    </item>
    <item>
      <title>Re: How to upgrade and patch for wpa2 KRACK?</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/How-to-upgrade-and-patch-for-wpa2-KRACK/m-p/4604#M132</link>
      <description>Hello Jeronimo, Community, &lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; SZ 3.5.1 and 3.4.2 (latest native releases) install a .noarch.patch file.&amp;nbsp; If you have Zones&lt;BR /&gt;under 3.5.1 or 3.4.2 for versions 3.2.1 or 3.1.2, you install .ksp files.&amp;nbsp; Please see the descriptions&lt;BR /&gt;on the SZ firmware download pages. They have the exact filenames and extentions for your&lt;BR /&gt;reference.&amp;nbsp; SZ-100 and vSZ-E controllers need to be upgraded to 3.4.2 or 3.5.1 presently.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/software/1481-smartzone-3-5-1-mr1-patch1-software-release-wpa2-krack-patch" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/software/1481-smartzone-3-5-1-mr1-patch1-software-release-wpa2-krack-patch"&gt;https://support.ruckuswireless.com/software/1481-smartzone-3-5-1-mr1-patch1-software-release-wpa2-kr...&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/software/1482-smartzone-3-4-2-mr2-patch2-software-release-wpa2-krack-patch" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/software/1482-smartzone-3-4-2-mr2-patch2-software-release-wpa2-krack-patch"&gt;https://support.ruckuswireless.com/software/1482-smartzone-3-4-2-mr2-patch2-software-release-wpa2-kr...&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Management has decided to create .noarch.patch files to directly upgrade systems that are&lt;BR /&gt;running 3.2.1 and 3.1.2 in native mode (such as SZ-100/vSZ-E)&amp;nbsp;and ZD 9.7.2, and these should &lt;BR /&gt;come before the end of November.&lt;BR /&gt;&lt;BR /&gt;Please follow current status information on our Ruckus KRACK Support Resource Center page.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/krack-ruckus-wireless-support-resource-center" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/krack-ruckus-wireless-support-resource-center"&gt;https://support.ruckuswireless.com/krack-ruckus-wireless-support-resource-center&lt;/A&gt;</description>
      <pubDate>Wed, 01 Nov 2017 16:14:18 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/How-to-upgrade-and-patch-for-wpa2-KRACK/m-p/4604#M132</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-11-01T16:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to upgrade and patch for wpa2 KRACK?</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/How-to-upgrade-and-patch-for-wpa2-KRACK/m-p/4605#M133</link>
      <description>The Ruckus AP CLI scripts for SZ 3.1.2 - 3.5.1 will disable EAPOL retries, to protect wireless clients &lt;BR /&gt;that do not have WPA2 KRACK fix firmware upgrades.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://support.ruckuswireless.com/software/1487-smartzone-3-1-2-3-5-1-software-release-ap-cli-scripts-wpa2-krack-patch" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/software/1487-smartzone-3-1-2-3-5-1-software-release-ap-cli-scripts-wpa2-krack-patch"&gt;https://support.ruckuswireless.com/software/1487-smartzone-3-1-2-3-5-1-software-release-ap-cli-scrip...&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Apple has released iOS 11.1 wich includes fixes for the KRACK vulnerabilities:&amp;nbsp;&amp;nbsp;&lt;A href="https://support.apple.com/en-us/HT208222" rel="nofollow" target="_blank" title="Link https//supportapplecom/en-us/HT208222"&gt;https://support.apple.com/en-us/HT208222&lt;/A&gt;
&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
Available for: iPhone 7 and later, and iPad Pro 9.7-inch (early 2016) and later&lt;BR /&gt;&lt;BR /&gt;
Impact: An attacker in Wi-Fi range may force nonce reuse in WPA clients (Key Reinstallation Attacks - KRACK)&lt;BR /&gt;&lt;BR /&gt;
Description: A logic issue existed in the handling of state transitions. This was addressed with improved state management.&lt;BR /&gt;&lt;BR /&gt;
&lt;SPAN&gt;CVE-2017-13080: Mathy Vanhoef of the imec-DistriNet group at KU Leuven&lt;/SPAN&gt;</description>
      <pubDate>Wed, 01 Nov 2017 16:30:02 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/How-to-upgrade-and-patch-for-wpa2-KRACK/m-p/4605#M133</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-11-01T16:30:02Z</dc:date>
    </item>
  </channel>
</rss>

