d33tah / call-for-wpa3 Goto Github PK

The problem of the captive portals is actually solved, but through DHCP.

They added a new option (number 160 for IPv4 and 103 for IPv6) to inform the client requesting an address that there is a portal on the specified URL.

Regards,

That Dutch guy who tasted some of your Tschunk at the SHA bar :)

We should compile a list of media contacts and send them a link to the call for WPA3 with a brief comment. This way we would reach awareness from the public.

This list would include Newspapers, Reddit, HackerNews, Tech Blogs, Tech News sites and more.

State-of-the-art password authentication uses PAKE, which completely prevents bruteforcing passwords: https://en.wikipedia.org/wiki/Password-authenticated_key_agreement See also https://news.ycombinator.com/item?id=14842145

The suggestions to use scrypt or PBKDF2 (under The password can be cracked offline) are obsoleted by PAKE.

WPA3 was finally teased by the WiFi alliance here: https://www.wi-fi.org/news-events/newsroom/wi-fi-alliance-introduces-security-enhancements

We should look for information and check what issues pointed here are addressed and push for the others to be implemented.

https://github.com/P-H-C/phc-winner-argon2#argon2

Is it too late to point out that there seems to be no discussion of how WPA3 will close hole196? It is a problem for WPA2 Enterprise APs that circumvents VLAN isolation. Those of us who use WPA2 Enterprise in our homes would appreciate a fix for Hole196.