This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
- Community
- RUCKUS Technologies
- RUCKUS Lennar Support
- Community Services
- RTF
- RTF Community
- Australia and New Zealand – English
- Brazil – Português
- China – 简体中文
- France – Français
- Germany – Deutsch
- Hong Kong – 繁體中文
- India – English
- Indonesia – bahasa Indonesia
- Italy – Italiano
- Japan – 日本語
- Korea – 한국어
- Latin America – Español (Latinoamérica)
- Middle East & Africa – English
- Netherlands – Nederlands
- Nordics – English
- North America – English
- Poland – polski
- Russia – Русский
- Singapore, Malaysia, and Philippines – English
- Spain – Español
- Taiwan – 繁體中文
- Thailand – ไทย
- Turkey – Türkçe
- United Kingdom – English
- Vietnam – Tiếng Việt
- EOL Products
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- RUCKUS Forums
- RUCKUS Technologies
- Cloudpath
- Re: Severe flaw in WPA2 - cracked
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Severe flaw in WPA2 - cracked
Anonymous
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-15-2017 11:27 PM
when can we expect to see update for this https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-tra...
153 REPLIES 153
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2017 04:54 AM
Patching APs against vulnerabilities is a part of a network security. I don't see Ruckus delivering.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2017 06:26 AM
Robert, it doesn't matter if they own the whole picture or not, they have demonstrated they don't care about ANY of it.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2017 06:37 AM
I think you're being a little harsh here. Yes they were late to the party with regards to an announcement vs many of the other enterprise vendors. However, they are not the only ones who are yet to release patch firmware. Cisco for example has currently only one level of controller firmware with a fix for all AP types, 8.3.130.0. All others show as TBD. If i have something in the next day or so then i will be satisfied (not happy) about the response time on firmware but i still find the delay on an announcement, especially when it didn't include a date/time for firmware release to be unacceptable.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-17-2017 06:52 AM
I don't think he is too harsh here, cause the are sitting on it since july. Yes he should blame cisco also but we are here about ruckus. As I wrote I have some expection to an enterprise support:
1. No out of office notification if someone mails to your security contact ([email protected])
This E-mail has to go to an high priorized and monitored queue in an ticket
system,
2. That your support people and partners would inform one or two day's before
the public disclosure.
3. That you have the right communication for all your customers ready and put
it in the right time on the right places (webside, newsletter, twitter...)
4. That you have your firmware fixes ready to deploy and if it is possible
some advanced monitoring ready for this issue and for broken clients.
and nothing had happened. If they would know from the problem since yesterday we can discuss, but not sitting since months on it....
1. No out of office notification if someone mails to your security contact ([email protected])
This E-mail has to go to an high priorized and monitored queue in an ticket
system,
2. That your support people and partners would inform one or two day's before
the public disclosure.
3. That you have the right communication for all your customers ready and put
it in the right time on the right places (webside, newsletter, twitter...)
4. That you have your firmware fixes ready to deploy and if it is possible
some advanced monitoring ready for this issue and for broken clients.
and nothing had happened. If they would know from the problem since yesterday we can discuss, but not sitting since months on it....
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-18-2017 01:30 PM
Yesterday I opened a support case about poor wifi performance after upgrading to the latest firmware. A tech promised to call me today at 3pm. Well, no call at 3pm, 4pm or 5pm. Replied to email I got ([email protected]) and guess what? Got out of office reply! I'm speechless.
