-
Notifications
You must be signed in to change notification settings - Fork 542
[TW#20355] ESP-NOW encryption #114
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
Comments
Hi Tareq-Sulaiman, Here is an example of esp-now:
|
Well thank you very much for responding @Junhao-Espressif ! |
If I don't use my own keys does ESP-NOW use a default key and therefore encrypt all communications in any way ? If so what level of encryption is enabled by default ? |
Something is completely broken :( Here's the situation: A) Controller (no crypto) -> Slave (no crypto) = ok In other words - the slave can't verify if the controller used any crypto at all. There is no way for the slave to authenticate the controller. I might be doing something wrong .. but .. what? m. |
I have discovered the same thing, did you manage to find a fix? How come anyone with ESP can spoof and send data to my Slave (with crypto) |
Has anything happened with this issue? Just noticed the same behaviour today and it's a major security concern. |
There seems to be a lack of information in the documentation about how to set a key for the communication in ESP-NOW.
it all works fine until I add an encryption key in the master device, then the receiver does not receive data anymore.
When I add the key, the send callback still registers a value 0 for the status register, which implies that the receiver should receive data properly, yet it is not happening.
And if I use a NULL key does the data get sent unencrypted? or does it get encrypted but with a default key.
The text was updated successfully, but these errors were encountered: