<?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 Community Update from Dan Rabinovitsj, Ruckus COO in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Community-Update-from-Dan-Rabinovitsj-Ruckus-COO/m-p/3226#M173</link>
    <description>This is a message to Ruckus partners and customers from Dan Rabinovitsj, Ruckus COO:&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE&gt;
To Ruckus partners and customers from Dan Rabinovitsj, COO:&lt;BR /&gt;&lt;BR /&gt;
We recognize that many of you are understandably displeased&amp;nbsp;and frustrated&amp;nbsp;with the delay in our initial acknowledgment of the WPA2 vulnerabilities and in our response timeline.&amp;nbsp;We assessed the practical risk of a vulnerability as low and that guided our plans&amp;nbsp;to address the issue and how we communicated with our customers and partners.&amp;nbsp; We continue to assess that the relative risk&amp;nbsp;to our customers’ networks&amp;nbsp;around this vulnerability&amp;nbsp;as&amp;nbsp;low and&amp;nbsp;that&amp;nbsp;while the need to patch is urgent it does not constitute an emergency.&amp;nbsp; However, we clearly underestimated the media reaction, resulting&amp;nbsp;in&amp;nbsp;perception issues around Wi-Fi vulnerability, and&amp;nbsp;putting our customers&amp;nbsp;and partners in a difficult position.&amp;nbsp; In retrospect, we should have acted more quickly and prioritized the communications&amp;nbsp;and&amp;nbsp;made a patch available on&amp;nbsp;day 1.&amp;nbsp; We recognize our judgement call has caused some of our customers to think we don’t care about their security.&amp;nbsp; Nothing could be further from the truth. We will continue to provide updates on work-arounds and patches and will&amp;nbsp;learn from this experience.&amp;nbsp; This is the highest priority for our team. We appreciate your business and honest feedback and will do better in the future.&lt;BR /&gt;&lt;BR /&gt;
&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;
Please use this Community Update discussion thread to provide feedback Dan requested above.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
Please use the thread at &lt;A href="https://forums.ruckuswireless.com/ruckuswireless/topics/wpa2-krack-questions-answers-resource-page" rel="nofollow" target="_blank" title="Link https//forumsruckuswirelesscom/ruckuswireless/topics/wpa2-krack-questions-answers-resource-page"&gt;https://forums.ruckuswireless.com/ruckuswireless/topics/wpa2-krack-questions-answers-resource-page&lt;/A&gt; to focus on technical Q&amp;amp;A about WPA2 KRACK threat mitigation.&amp;nbsp;</description>
    <pubDate>Thu, 19 Oct 2017 20:38:15 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2017-10-19T20:38:15Z</dc:date>
    <item>
      <title>Community Update from Dan Rabinovitsj, Ruckus COO</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Community-Update-from-Dan-Rabinovitsj-Ruckus-COO/m-p/3226#M173</link>
      <description>This is a message to Ruckus partners and customers from Dan Rabinovitsj, Ruckus COO:&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE&gt;
To Ruckus partners and customers from Dan Rabinovitsj, COO:&lt;BR /&gt;&lt;BR /&gt;
We recognize that many of you are understandably displeased&amp;nbsp;and frustrated&amp;nbsp;with the delay in our initial acknowledgment of the WPA2 vulnerabilities and in our response timeline.&amp;nbsp;We assessed the practical risk of a vulnerability as low and that guided our plans&amp;nbsp;to address the issue and how we communicated with our customers and partners.&amp;nbsp; We continue to assess that the relative risk&amp;nbsp;to our customers’ networks&amp;nbsp;around this vulnerability&amp;nbsp;as&amp;nbsp;low and&amp;nbsp;that&amp;nbsp;while the need to patch is urgent it does not constitute an emergency.&amp;nbsp; However, we clearly underestimated the media reaction, resulting&amp;nbsp;in&amp;nbsp;perception issues around Wi-Fi vulnerability, and&amp;nbsp;putting our customers&amp;nbsp;and partners in a difficult position.&amp;nbsp; In retrospect, we should have acted more quickly and prioritized the communications&amp;nbsp;and&amp;nbsp;made a patch available on&amp;nbsp;day 1.&amp;nbsp; We recognize our judgement call has caused some of our customers to think we don’t care about their security.&amp;nbsp; Nothing could be further from the truth. We will continue to provide updates on work-arounds and patches and will&amp;nbsp;learn from this experience.&amp;nbsp; This is the highest priority for our team. We appreciate your business and honest feedback and will do better in the future.&lt;BR /&gt;&lt;BR /&gt;
&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;
Please use this Community Update discussion thread to provide feedback Dan requested above.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;
Please use the thread at &lt;A href="https://forums.ruckuswireless.com/ruckuswireless/topics/wpa2-krack-questions-answers-resource-page" rel="nofollow" target="_blank" title="Link https//forumsruckuswirelesscom/ruckuswireless/topics/wpa2-krack-questions-answers-resource-page"&gt;https://forums.ruckuswireless.com/ruckuswireless/topics/wpa2-krack-questions-answers-resource-page&lt;/A&gt; to focus on technical Q&amp;amp;A about WPA2 KRACK threat mitigation.&amp;nbsp;</description>
      <pubDate>Thu, 19 Oct 2017 20:38:15 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Community-Update-from-Dan-Rabinovitsj-Ruckus-COO/m-p/3226#M173</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-10-19T20:38:15Z</dc:date>
    </item>
  </channel>
</rss>

