<?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: Severe flaw in WPA2 - cracked in Cloudpath Enrollment System (ES)</title>
    <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25489#M205</link>
    <description>hi,&lt;BR /&gt;&lt;BR /&gt;I have read the Ruckus Security Advisory and also&lt;BR /&gt;&lt;A href="https://theruckusroom.ruckuswireless.com/wi-fi/2017/10/16/commonsense-approach-uncommon-problem/" rel="nofollow" target="_blank" title="Link https//theruckusroomruckuswirelesscom/wi-fi/2017/10/16/commonsense-approach-uncommon-problem/"&gt;https://theruckusroom.ruckuswireless.com/wi-fi/2017/10/16/commonsense-approach-uncommon-problem/ &lt;/A&gt;and many other stuff. &lt;BR /&gt;&lt;BR /&gt;This all show ruckus in a very bad light. Can we still trust?&lt;BR /&gt;&lt;BR /&gt;Ruckus was informed many weeks/months ago about this issue and the disclosure date. &lt;BR /&gt;&lt;BR /&gt;But the customers was left alone!!&lt;BR /&gt;&lt;BR /&gt;I was informed since two day's (CET timezone) about this issue. I waited for&lt;BR /&gt;the public disclosure yesterday and opened a case at ruckus cause no information &lt;BR /&gt;about it was found online. &lt;BR /&gt;&lt;BR /&gt;All other major vendors did have the updates ready and informed their customers&lt;BR /&gt;at the same time the issue was going public. They had their communication ready&lt;BR /&gt;and send it out to their partners and customers at the right time.&lt;BR /&gt;&lt;BR /&gt;Ruckus didn't they don't even inform the partners!!&lt;BR /&gt;&lt;BR /&gt;What I as customer with contract and as partner has expected:&lt;BR /&gt;&lt;BR /&gt;1. No out of office notification if someone mails to your security contact (&lt;A href="mailto:security@ruckuswireless.com" rel="nofollow"&gt;security@ruckuswireless.com&lt;/A&gt;)&lt;BR /&gt;&amp;nbsp;&amp;nbsp; This E-mail has to go to an high priorized and monitored queue in an ticket&lt;BR /&gt;&amp;nbsp;&amp;nbsp; system,&lt;BR /&gt;&lt;BR /&gt;2. That your support people and partners would inform one or two day's before&lt;BR /&gt;&amp;nbsp;&amp;nbsp; the public disclosure.&lt;BR /&gt;&lt;BR /&gt;3. That you have the right communication for all your customers ready and put&lt;BR /&gt;&amp;nbsp;&amp;nbsp; it in the right time on the right places (webside, newsletter, twitter...)&lt;BR /&gt;&lt;BR /&gt;4. That you have your firmware fixes ready to deploy and if it is possible&lt;BR /&gt;&amp;nbsp;&amp;nbsp; some advanced monitoring ready for this issue and for broken clients.&lt;BR /&gt;&lt;BR /&gt;What I now expect:&lt;BR /&gt;&lt;BR /&gt;1. really fast update availability, even for older systems and without contract*&lt;BR /&gt;&lt;BR /&gt;2. transparent communication what went wrong and why&lt;BR /&gt;&lt;BR /&gt;3. better documentation and reporting how to fix the problem in our company's,&lt;BR /&gt;&amp;nbsp;&amp;nbsp; not even on the wireless system side:&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; * How to detect clients with this problem&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; * For which clients are updates available &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I'm located in germany, the public&amp;nbsp; disclosure was now nearly 24hour away,&lt;BR /&gt;even the radio stations here&amp;nbsp; broadcast informations about this issue faster&lt;BR /&gt;then you. &lt;BR /&gt;&lt;BR /&gt;At this morning the German Federal Office for Information Security has send out&lt;BR /&gt;an public announcement that all people should update their clients and&lt;BR /&gt;accesspoints / routers if possible or contact their vendors for updates. &lt;BR /&gt;&lt;BR /&gt;The phones are ringing with customers, cto's and so on. All want to have a&lt;BR /&gt;status about this issue and a dead line then it is fixed.&lt;BR /&gt;&lt;BR /&gt;Yes the major problem are the client's, but the accespoints and controllers&lt;BR /&gt;should be fixed also and I expect that I get some help from my wireless system&lt;BR /&gt;to detect the problem on the clients if I have a managed wireless solution &lt;BR /&gt;not one single accesspoint.&lt;BR /&gt;&lt;BR /&gt;Our company has already rolled out the patcheѕ for our clients. &lt;BR /&gt;Even microsoft has the patches already in place. &lt;BR /&gt;&lt;BR /&gt;For me it looks like ruckus has ignored the advisory and now the &lt;BR /&gt;try to react on it. This has nothing todo with enterprise support!!&lt;BR /&gt;&lt;BR /&gt;There is absolute no excuse for this!! &lt;BR /&gt;&lt;BR /&gt;For me the trust in your security support is gone, and there must &lt;BR /&gt;be very good arguments that we will stay with ruckus after our contract &lt;BR /&gt;ended. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;* cause how it was happend (see what I expected)</description>
    <pubDate>Tue, 17 Oct 2017 08:26:58 GMT</pubDate>
    <dc:creator>ruben_herold</dc:creator>
    <dc:date>2017-10-17T08:26:58Z</dc:date>
    <item>
      <title>Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25418#M134</link>
      <description>when can we expect to see update for this&amp;nbsp;&lt;A href="https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-traffic-open-to-eavesdropping/" rel="nofollow" target="_blank" title="Link https//arstechnicacom/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-traffic-open-to-eavesdropping/"&gt;https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-traffic-open-to-eavesdropping/&lt;/A&gt;</description>
      <pubDate>Mon, 16 Oct 2017 06:27:01 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25418#M134</guid>
      <dc:creator>marko_teklic</dc:creator>
      <dc:date>2017-10-16T06:27:01Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25419#M135</link>
      <description>"One researcher told Ars that Aruba and Ubiquiti, ..., already have updates available to patch or mitigate the vulnerabilities."&lt;BR /&gt;&lt;BR /&gt;Well, let's see how fast our support-contract money work..</description>
      <pubDate>Mon, 16 Oct 2017 07:27:06 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25419#M135</guid>
      <dc:creator>jakob_peterh_ns</dc:creator>
      <dc:date>2017-10-16T07:27:06Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25420#M136</link>
      <description>Some vendors like mikrotik have already rolled out patched versions since weeks:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://forum.mikrotik.com/viewtopic.php?f=21&amp;amp;t=126695" rel="nofollow" target="_blank" title="Link https//forummikrotikcom/viewtopicphpf21t126695"&gt;https://forum.mikrotik.com/viewtopic.php?f=21&amp;amp;t=126695&lt;/A&gt;</description>
      <pubDate>Mon, 16 Oct 2017 09:00:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25420#M136</guid>
      <dc:creator>ruben_herold</dc:creator>
      <dc:date>2017-10-16T09:00:39Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25421#M137</link>
      <description>I too would like an answer to this. And for our patch to be made available quickly. We already have clients asking.</description>
      <pubDate>Mon, 16 Oct 2017 10:02:51 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25421#M137</guid>
      <dc:creator>james_julier</dc:creator>
      <dc:date>2017-10-16T10:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25422#M138</link>
      <description>Me too for my R600 Unleashed ...</description>
      <pubDate>Mon, 16 Oct 2017 10:08:33 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25422#M138</guid>
      <dc:creator>rw_van_der_knoo</dc:creator>
      <dc:date>2017-10-16T10:08:33Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25423#M139</link>
      <description>Yes, this breach is annoying.&lt;BR /&gt;&lt;BR /&gt;But .. have been evangelizing for years that wifi should only be used as transport for VPN (OpenVPN).&lt;BR /&gt;&lt;BR /&gt;Have been trying to find more information like press releases or other material on topics like Ruckus and WPA2 krack. (&lt;A href="https://www.krackattacks.com/" rel="nofollow" target="_blank" title="Link https//wwwkrackattackscom/"&gt;https://www.krackattacks.com/&lt;/A&gt;)&lt;BR /&gt;&lt;BR /&gt;Notice that this all has been released earlier to manufacturers and only now will go public, meaning that only some manufacturers have reacted to research papers: &lt;A href="https://eprint.iacr.org/2016/475.pdf" rel="nofollow" target="_blank" title="Link https//eprintiacrorg/2016/475pdf"&gt;https://eprint.iacr.org/2016/475.pdf&lt;/A&gt;&lt;BR /&gt;Dated May-17 2016 .. it was all there.</description>
      <pubDate>Mon, 16 Oct 2017 10:13:14 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25423#M139</guid>
      <dc:creator>ari_lemmke</dc:creator>
      <dc:date>2017-10-16T10:13:14Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25424#M140</link>
      <description>Ruckus, you're late to the party as usual. When will we see firmware updates to address KRACK?</description>
      <pubDate>Mon, 16 Oct 2017 10:13:59 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25424#M140</guid>
      <dc:creator>tech_support_4y</dc:creator>
      <dc:date>2017-10-16T10:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25425#M141</link>
      <description>I would dearly love to see this ASAP as we need to start change management procedures.</description>
      <pubDate>Mon, 16 Oct 2017 10:55:37 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25425#M141</guid>
      <dc:creator>thomas_barnsley</dc:creator>
      <dc:date>2017-10-16T10:55:37Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25426#M142</link>
      <description>I've raised a P2 Case (ID: 00565627).&lt;BR /&gt;&lt;BR /&gt;According to the security section of the Ruckus site (&lt;A href="https://www.ruckuswireless.com/security" rel="nofollow" target="_blank" title="Link https//wwwruckuswirelesscom/security"&gt;https://www.ruckuswireless.com/security&lt;/A&gt;) the CVE's covered by Krack have not been addressed.&lt;BR /&gt;&lt;BR /&gt;Kind Regards,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Andy.</description>
      <pubDate>Mon, 16 Oct 2017 11:05:44 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25426#M142</guid>
      <dc:creator>andrew_bailey_7</dc:creator>
      <dc:date>2017-10-16T11:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25427#M143</link>
      <description>This is big, ruckus had better act quickly on this. I also expect them to release patches for some of the older chains of firmware. We have perfectly usable 802.11n access points (7363) in use that are locked to the 9.12.x chain. It would pretty much mean the end of our relationship with ruckus if we were forced to upgrade these for a security patch.&amp;nbsp;</description>
      <pubDate>Mon, 16 Oct 2017 12:30:40 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25427#M143</guid>
      <dc:creator>dustin_roberts_</dc:creator>
      <dc:date>2017-10-16T12:30:40Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25428#M144</link>
      <description>Aruba has released fixes for older versions of firmware but only ones the deem 'under support'. Ruckus doesn't view firmware in the same way but based on the fact that the recommended 9.13.3.0.121 i would expect them to be going back a little way on the firmware list at least to 9.12&amp;nbsp;</description>
      <pubDate>Mon, 16 Oct 2017 12:36:33 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25428#M144</guid>
      <dc:creator>robert_lowe_722</dc:creator>
      <dc:date>2017-10-16T12:36:33Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25429#M145</link>
      <description>Yep, end of support for the ZoneDirector 1100 for example is June 30th 2020, and it is stuck on&amp;nbsp;&lt;A href="https://support.ruckuswireless.com/software/1078-zd1100-9-10-2-0-29-mr2-refresh-software-release" rel="nofollow" target="_blank" title="Link https//supportruckuswirelesscom/software/1078-zd1100-9-10-2-0-29-mr2-refresh-software-release"&gt;ZD1100 9.10.2.0.29 (MR2 Refresh) Software Release&lt;/A&gt;&lt;BR /&gt;I would expect an update for this from Ruckus very soon.</description>
      <pubDate>Mon, 16 Oct 2017 12:40:17 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25429#M145</guid>
      <dc:creator>tech_support_4y</dc:creator>
      <dc:date>2017-10-16T12:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25430#M146</link>
      <description>My understand is that this issue was something vendors were previously notified about. &amp;nbsp;So, the fact that there doesn't even appear to be a proposed timeline for a fix is not acceptable - especially since some vendors are already releasing patches.&lt;BR /&gt;&lt;BR /&gt;Very frustrating.</description>
      <pubDate>Mon, 16 Oct 2017 12:44:02 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25430#M146</guid>
      <dc:creator>mloiterman</dc:creator>
      <dc:date>2017-10-16T12:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25431#M147</link>
      <description>Aruba reports that they were informed by the author of the research paper in July &amp;amp; by CERT in August. Imagine same for all vendors. Plus many (if not all) have been participating in industry level discussions</description>
      <pubDate>Mon, 16 Oct 2017 12:48:38 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25431#M147</guid>
      <dc:creator>robert_lowe_722</dc:creator>
      <dc:date>2017-10-16T12:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25432#M148</link>
      <description>Pretty annoying issue and surely not the best time to get it public, but I don't get why this issue is still persistent since it was reported to the vendors in August/Septembre.&amp;nbsp; Actually there's one customer after another calling and asking what they can do and when they can expect a solution. Not cool, to have no answer ready...</description>
      <pubDate>Mon, 16 Oct 2017 12:50:19 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25432#M148</guid>
      <dc:creator>simon_b_hrer_73</dc:creator>
      <dc:date>2017-10-16T12:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25433#M149</link>
      <description>Dont forget though that the infrastructure is only part of this issue. Even after controllers &amp;amp; AP's have had a 'fix' applied there are still vulnerabilities from the client side, which is actually the source of the issue, can only be addressed by the client manufacturers. As i understand it, It affects infrastructure vendors because sometimes their AP's act as a client like when using mesh for example.&lt;BR /&gt;&lt;BR /&gt;Here's a link to their FAQ on the issue:&amp;nbsp;&lt;A href="http://www.arubanetworks.com/assets/alert/ARUBA-PSA-2017-007_FAQ_Rev-1.pdf" rel="nofollow" title="Link: http://www.arubanetworks.com/assets/alert/ARUBA-PSA-2017-007_FAQ_Rev-1.pdf"&gt;http://www.arubanetworks.com/assets/alert/ARUBA-PSA-2017-007_FAQ_Rev-1.pdf&lt;/A&gt;</description>
      <pubDate>Mon, 16 Oct 2017 12:54:32 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25433#M149</guid>
      <dc:creator>robert_lowe_722</dc:creator>
      <dc:date>2017-10-16T12:54:32Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25434#M150</link>
      <description>And here's Meraki's which is excellent IMO:&lt;BR /&gt;&lt;A href="https://documentation.meraki.com/zGeneral_Administration/Support/802.11r_Vulnerability_(CVE%3A_2017-13082)_FAQ" rel="nofollow" target="_blank" title="Link: https://documentation.meraki.com/zGeneral_Administration/Support/802.11r_Vulnerability_(CVE%3A_2017-13082)_FAQ"&gt;https://documentation.meraki.com/zGeneral_Administration/Support/802.11r_Vulnerability_(CVE%3A_2017-...&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Deathly silence&amp;nbsp;from Ruckus...</description>
      <pubDate>Mon, 16 Oct 2017 14:25:13 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25434#M150</guid>
      <dc:creator>tech_support_4y</dc:creator>
      <dc:date>2017-10-16T14:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25435#M151</link>
      <description>Agree, they knew about this august 28. Why is a patch not already available.&amp;nbsp;</description>
      <pubDate>Mon, 16 Oct 2017 14:30:08 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25435#M151</guid>
      <dc:creator>dustin_roberts_</dc:creator>
      <dc:date>2017-10-16T14:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25436#M152</link>
      <description>From my chat session they plan to take their time... They have a response slated for the second half of today.</description>
      <pubDate>Mon, 16 Oct 2017 14:42:10 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25436#M152</guid>
      <dc:creator>jesse_johnston_</dc:creator>
      <dc:date>2017-10-16T14:42:10Z</dc:date>
    </item>
    <item>
      <title>Re: Severe flaw in WPA2 - cracked</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25437#M153</link>
      <description>I guess that depends on where you are......In the UK its already the 2nd half of today &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;</description>
      <pubDate>Mon, 16 Oct 2017 14:49:00 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/Severe-flaw-in-WPA2-cracked/m-p/25437#M153</guid>
      <dc:creator>robert_lowe_722</dc:creator>
      <dc:date>2017-10-16T14:49:00Z</dc:date>
    </item>
  </channel>
</rss>

