<?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: KRACK attack on WPA2 in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20973#M1445</link>
    <description>Hi All,&lt;BR /&gt;
&lt;BR /&gt;
Extreme Networks has been released WiNG 5.8.6.8 - &lt;A href="http://documentation.extremenetworks.com/release_notes/WiNG/9035063-02_WiNG_5_8_6_8_Release_Notes.pdf" target="_blank" rel="nofollow noreferrer noopener"&gt;WiNG 5.8.6.8 Release Notes&lt;/A&gt;.&lt;BR /&gt;
&lt;BR /&gt;
In this release, we add to address some of WPA2 KRACK vulnerabilities for "Client Bridge" mode as well as support for sensor KRACK signature (ADSP release with that  functionality should be released shortly).&lt;BR /&gt;
&lt;BR /&gt;
Best regards,&lt;BR /&gt;
Bin&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Wed, 06 Dec 2017 06:56:00 GMT</pubDate>
    <dc:creator>Bin</dc:creator>
    <dc:date>2017-12-06T06:56:00Z</dc:date>
    <item>
      <title>KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20896#M1368</link>
      <description>Hello everyone,&lt;BR /&gt;
I have some questions due to the expected disclosure today on the attack possible on WPA2 SSIDs.&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;US-CERT has become aware of several key management vulnerabilities in the 4-way handshake of the Wi-Fi Protected Access II (WPA2) security protocol. The impact of exploiting these vulnerabilities includes decryption, packet replay, TCP connection hijacking, HTTP content injection, and others. Note that as protocol-level issues, most or all correct implementations of the standard will be affected. The CERT/CC and the reporting researcher KU Leuven, will be publicly disclosing these vulnerabilities on 16 October 2017.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;
&lt;BR /&gt;
Link: &lt;A href="https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-traffic-open-to-eavesdropping/" target="_blank" rel="nofollow noreferrer noopener"&gt;https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-tra...&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
- Is Extreme aware of this?&lt;BR /&gt;
- Are Fixes ready to be released?&lt;BR /&gt;
- Is a software fix sufficient or does hardware need to be replaced?&lt;BR /&gt;
&lt;BR /&gt;
Thanks and best regards,&lt;BR /&gt;
&lt;BR /&gt;
Johannes</description>
      <pubDate>Mon, 16 Oct 2017 11:47:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20896#M1368</guid>
      <dc:creator>Johannes_Dennin</dc:creator>
      <dc:date>2017-10-16T11:47:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20897#M1369</link>
      <description>Hi Johannes,&lt;BR /&gt;
&lt;BR /&gt;
Extreme is fast but not that fast, from what I'd read in the web the guys that found the vulnerability will release more information how it works in 5 hours.&lt;BR /&gt;
&lt;BR /&gt;
I'm very confident that Extreme will implement a fix.&lt;BR /&gt;
&lt;BR /&gt;
Cheers,&lt;BR /&gt;
Ron</description>
      <pubDate>Mon, 16 Oct 2017 11:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20897#M1369</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-10-16T11:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20898#M1370</link>
      <description>Extreme was notified in August like the other vendors. &lt;A href="https://www.kb.cert.org/vuls/id/228519/" target="_blank" rel="nofollow noreferrer noopener"&gt;https://www.kb.cert.org/vuls/id/228519/&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://www.kb.cert.org/vuls/id/CHEU-AQNN43" target="_blank" rel="nofollow noreferrer noopener"&gt;https://www.kb.cert.org/vuls/id/CHEU-AQNN43&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 11:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20898#M1370</guid>
      <dc:creator>Steve_Burke</dc:creator>
      <dc:date>2017-10-16T11:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20899#M1371</link>
      <description>This is my concern as well.  Many other major vendors had a fix that was already put into previous updates or was released yesterday.  I would have expected the same from Extreme, but that doesn't seem to be the case.</description>
      <pubDate>Mon, 16 Oct 2017 11:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20899#M1371</guid>
      <dc:creator>JP4</dc:creator>
      <dc:date>2017-10-16T11:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20900#M1372</link>
      <description>I'm curious too. Could someone from Extreme shed some light on this?</description>
      <pubDate>Mon, 16 Oct 2017 11:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20900#M1372</guid>
      <dc:creator>Johannes_Dennin</dc:creator>
      <dc:date>2017-10-16T11:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20901#M1373</link>
      <description>Extreme Networks was notified by the CERT regarding the KRACK vulnerability, which was subsequently communicated to the Engineering team. The team is working on a solution to be completed by end of this week (10/20). We are reviewing procedures to confirm vulnerability response urgency meets expectations. Thanks for your patience.&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 11:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20901#M1373</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2017-10-16T11:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20902#M1374</link>
      <description>I suppose, engineering team would be releasing patches not only to latest WING firmware (5.9.1) but also to previous series (i.e. 5.8.4) as we have some VX-based installations with multiple types of APs in place (622,650,75xx). Thanks for confirmation. &lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 11:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20902#M1374</guid>
      <dc:creator>Karol_Radosovsk</dc:creator>
      <dc:date>2017-10-16T11:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20903#M1375</link>
      <description>Please take a look into the Vulnerability Notice.....&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://extremeportal.force.com/ExtrArticleDetail?n=000018005" target="_blank" rel="nofollow noreferrer noopener"&gt;https://extremeportal.force.com/ExtrArticleDetail?n=000018005&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 11:59:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20903#M1375</guid>
      <dc:creator>Ronald_Dvorak</dc:creator>
      <dc:date>2017-10-16T11:59:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20904#M1376</link>
      <description>I was just asking because other vendors apparently have updates available / in beta. But I guess we'll see soon what all the fuss is about!</description>
      <pubDate>Mon, 16 Oct 2017 14:10:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20904#M1376</guid>
      <dc:creator>Johannes_Dennin</dc:creator>
      <dc:date>2017-10-16T14:10:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20905#M1377</link>
      <description>The corresponding paper:&lt;BR /&gt;
"Key Reinstallation Attacks: Forcing Nonce Reuse in WPA2"&lt;BR /&gt;
&lt;A href="https://papers.mathyvanhoef.com/ccs2017.pdf" target="_blank" rel="nofollow noreferrer noopener"&gt;https://papers.mathyvanhoef.com/ccs2017.pdf&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 16:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20905#M1377</guid>
      <dc:creator>Daniel_Bernhard</dc:creator>
      <dc:date>2017-10-16T16:42:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20906#M1378</link>
      <description>A different article I read indicated that vendors were made aware of this a couple months ago.  Hoping that maybe the fixes were put into a recent firmware release ?</description>
      <pubDate>Mon, 16 Oct 2017 16:58:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20906#M1378</guid>
      <dc:creator>JP4</dc:creator>
      <dc:date>2017-10-16T16:58:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20907#M1379</link>
      <description>There are updates from other vendors already:&lt;BR /&gt;
&lt;BR /&gt;
&lt;A href="https://www.reddit.com/r/KRaCK/comments/76pjf8/krack_megathread_check_back_often_for_updated/" target="_blank" rel="nofollow noreferrer noopener"&gt;https://www.reddit.com/r/KRaCK/comments/76pjf8/krack_megathread_check_back_often_for_updated/&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 17:02:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20907#M1379</guid>
      <dc:creator>Johannes_Dennin</dc:creator>
      <dc:date>2017-10-16T17:02:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20908#M1380</link>
      <description>I already have fixes for other vendor devices, but need them for the WiNG access points also, so same question.</description>
      <pubDate>Mon, 16 Oct 2017 18:23:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20908#M1380</guid>
      <dc:creator>Kyle_Stanford</dc:creator>
      <dc:date>2017-10-16T18:23:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20909#M1381</link>
      <description>I've asked the WiNG and IdentiFi teams for an update. I'll share with the thread when I have more information.&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 19:08:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20909#M1381</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2017-10-16T19:08:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20910#M1382</link>
      <description>And for the WLAN 9100 series from Avaya please!</description>
      <pubDate>Mon, 16 Oct 2017 19:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20910#M1382</guid>
      <dc:creator>Knut_Arne_Nygår</dc:creator>
      <dc:date>2017-10-16T19:13:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20911#M1383</link>
      <description>The Avaya 9100 series is still supported by Avaya. Unfortunately, I won't have an answer on that, but still may be able to get more information.&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 19:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20911#M1383</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2017-10-16T19:13:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20912#M1384</link>
      <description>Thanx. The product house and development (...) has moved to Extreme, probably not many left...?</description>
      <pubDate>Mon, 16 Oct 2017 19:13:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20912#M1384</guid>
      <dc:creator>Knut_Arne_Nygår</dc:creator>
      <dc:date>2017-10-16T19:13:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20913#M1385</link>
      <description>Really good summary here: &lt;A href="http://www.arubanetworks.com/assets/alert/ARUBA-PSA-2017-007_FAQ_Rev-1.pdf" target="_blank" rel="nofollow noreferrer noopener"&gt;http://www.arubanetworks.com/assets/alert/ARUBA-PSA-2017-007_FAQ_Rev-1.pdf&lt;/A&gt;</description>
      <pubDate>Mon, 16 Oct 2017 20:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20913#M1385</guid>
      <dc:creator>Andrew_Webster</dc:creator>
      <dc:date>2017-10-16T20:09:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20915#M1387</link>
      <description>I think so. From an email thread I saw earlier this morning, it sounds like someone is working to create a detection signature for this.&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 22:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20915#M1387</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2017-10-16T22:38:00Z</dc:date>
    </item>
    <item>
      <title>RE: KRACK attack on WPA2</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20916#M1388</link>
      <description>Hi James, I added some ADSP information to the article earlier this morning. It's in the repair recommendations section.&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Oct 2017 22:38:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/krack-attack-on-wpa2/m-p/20916#M1388</guid>
      <dc:creator>Drew_C</dc:creator>
      <dc:date>2017-10-16T22:38:00Z</dc:date>
    </item>
  </channel>
</rss>

