-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support the ESP8266_RTOS_SDK (WPA3 for the ESP8266) #2128
Comments
Thanks @Mat931 for pointing to the new SDK. Maybe this saves me from opening all my wall switches (about 40) and spending a lot of money. |
This would be fantastic. I have about two dozen devices that do not support protected management frames or WPA3. This is fairly bad because it means a hostile neighbor can just hack into that wireless network and screw with me / my cameras. It would be important to get this serious security hole in many ESPHome devices fixed. |
WPA2 is not insecure. It's not a "serious security hole". |
No but a "good" friend can still cause you headaches by sending repeated deauth frames in the air preventing your nodes from reconnecting to the AP. All he needs is an ESP8266... Good luck troubleshooting and defeating that... Minimum current recommendation would probably be to never use captive portal with arduino framework imho (which would be spawned automatically if connection to your wifi fails). |
Please note that PMF should be possible with WPA2 too. |
Afaik with upgrading the framework it's the same effort to bring PMF for WPA2 in, along with WPA3. See: https://github.com/alexCajas/esp8266RTOSArduCore This would bring the happiness of IDF to ESP8266 too... |
8266 needs to gain WPA3. Hundreds of thousands of people with dozens of devices each can't just have devices vulnerable to shitty encryption and deauth / reauth attacks. Replacing those devices which otherwise should be functional and up to spec would be an enormous cost to society. Most of the smart devices compatible with ESPHome sold today are 8266! And the chip is supported all the way up to 2026. What needs to be done in order to solve the issue? Will it require financial backing? I would be interested in helping that way. |
I would be happy to provide funding to anyone willing (and credible) to create a port of ESPHome that:
* uses ESP RTOS (which has support for WPA3)
* has basic support for GPIO for relays
* has support for UART
Please name a timeline and a price. Whatever the cost, I am likely to fund it. Obviously the work would be released as open source and incorporated into ESPHome. Half upfront half on master branch merge.
Serious offers only.
Thanks in advance.
|
It's a big stab but I think most of the steps to be done should follow the path of ESP32, when ESP-IDF was introduced. So it's not really from ground zero, as at least the way that has to be made should be familiar. It's indeed a lot of manual coding to do and thus I agree that a good financial offer to somebody willing to do it could speed up the process. Don't think that existing fulltime team members could handle it though. |
I completely agree. It's why I am willing do settle for the minimum set of features I outlined.
If anyone from the team or a volunteer with bona fides is willing to take me up on the offer, please post here. Whatever you need in terms of $ will be considered.
The potential to move millions of existing devices into the present and future is at hand.
|
Chiming in @stellar-aria from esphome/esphome#8106 might worth joining efforts, or at least consider the changes with respect to this too. |
Describe the problem you have/What new integration you would like
Please describe your use case for this integration and alternatives you've tried:
Additional context
The text was updated successfully, but these errors were encountered: