Aruba WPA3: The New Standard for Wi Fi Security

[@wweghorst]

Please close the microphone of people not presenting in the future to prevent all kind of disturbing sounds.

[@techieSudhakar]

Good Content and wonderful presentation on WPA3. Thanks!

[@wildyato37]

Tell me something You did manage to prevent manipulate the management frames..but what if the Victim left the AP/router on with WPA3 enabled and Attacker is already flooding deauth ayyacks on it...what will client do? Second Even if the Handshake process of SAE won't let the passkey to be Bruteforce ..but can be downgraded? even with WPA3 mode only Cuase communication I think if someone removed SAE protocols from it and remain the old WPA Handshake it would be possible?..

[@WR3ND]

7:42 My private WPA2-Personal PSKs are 1 of 47,672,401,706,823,533,450,263,330,816 - 16 random capital and lower case alphanumeric characters. Do you think that's good enough for the time being? I use WPA3 as well, but most all devices don't use it yet so I have separated guest networks, using either only WPA2 or only WPA3, not cross compatible WPA2/WPA3-Personal.

[@wildyato37]

Wait are you saying most Iot device doesn't support WPA3 yet?.😳 What are OEM and other vendors doing?.. Even Aliance said it is mandatory form WiFi 6 neworks😳

[@wildyato37]

You did a good thing to do that..well it's okay and Even people recommend this..🤔 So what you think you are protected or not .. it's upto you.

[@WR3ND]

@@wildyato37 I thought he was referring to brute force and dictionary lookup attacks, which can be hardened against with strong passwords. So, I am wondering if there are other vulnerabilities, or if he was just scare mongering.

[@WR3ND]

@@wildyato37 It isn't mandatory to use WPA3 on Wi-Fi 6 on clients, just that the option is there on access points and similar. They want backwards compatibility. You can even use hybrid WPA2/3 that can use either to connect to the same SSID, though this seems inherently compromised to an extent to me, so I don't use it, just WPA2 or WPA3 on separate guest networks.

[@wildyato37]

@@WR3ND Well From what I heard all about this standard...it still has flaws.. Indeed they mentioned the protection by using PMF to prevent flood attacks but wjat If Attacker may already have Flooding on a particular network to prevent connecting to clients anymore.. when starting the AP through power... Even There is no password detection system.. that some has really bhot your key..but when the attacker is inside of your network..😒 There Must be a somekind of table that only legitimate device has password. and locked the table...if anyone got password.. There will be Red light showing at LED lights...💀😂

[@richardherwig2136]

I really wish they had a formal process for questions. The one snide guy who keeps interrupting combined with the whispering and noises was distracting. The equally snide comments in the comment section really add nothing to the conversation, too. Par for the course, I guess. Still, good presentation and a great start for an open discussion on its merits.

[@MikeTrieu]

So he's one of the guys we have to blame for the Dragonblood vulnerabilities. Awesome.

[@cpuuk]

Maybe 2023 they will get this out officially.

[@aknightofgod]

and now 4 years later, adoption is great, amazing how fast technology moves. 6GHz coming :)

[@joyceandchrisaccount3644]

Too bad wpa3 security is broken. Almost like a spy agency designed it to be unsecured from the get go. Who would have thunk the first two iterations of wpa3 both used some form of elliptical curve encryption?