-
-
Notifications
You must be signed in to change notification settings - Fork 895
Mixed signing 2 #208
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
Mixed signing 2 #208
Conversation
only verify signature from nodes that require signing
Gateway only expects signing only from nodes it knows in turn require signed messages.
As the author of this pull request is not in my whitelist, I may not build this PR automatically. |
@fleinze Have you tested this change with a GW that require signatures, and two nodes (on that is "secure" and one that is "insecure")? I cannot currently verify the change myself I am afraid. But this is at least how it is supposed to work. Also, you should be able to set the GW to not require signatures, then the behavior should be like this: |
Jenkins, build this please |
thank you fallberg, I did test the usecases: |
Congratulations! I found no problems building this pull request for any of the supported boards or examples. |
@fleinze Ok, so all testcases did pass as expected? |
I just did final tests with a clean copy: (true means requires signing, false means doesn't require signing, as in the MySigning constructor) |
Gateway now correctly handles message signing
Thanks @fleinze for finding and fixing this! |
to match the description in http://forum.mysensors.org/topic/1021/security-introducing-signing-support-to-mysensors :