Signing clarification
-
Could some one confirm / clarify for me please.
I have a node that has #define MY_SIGNING_REQUEST_SIGNATURES defined.
My sensebender serial gateway does not have this definition set.
My node seemingly is randomly watchdog rebooting, which I have been endevouring to fault find for a while. It happened to occur whilsyt I was online with it, the last messages relating to signing exchanges.
my question is, Do I have to completely wipe my gateway eeprom, and reflash the gateway sketch to allow unsigned communications to this particular node? by removing #define MY_SIGNING_REQUEST_SIGNATURES, or Could I just delete the signing defines on the node ( didnt seem to work when I tried it)the nodes definitions are:
#define MY_SIGNING_SOFT
#define MY_SIGNING_SOFT_RANDOMSEED_PIN A6
#define MY_SIGNING_REQUEST_SIGNATURES -
Probably best to post the debug and put the out come through the log parser. I myself have no experience with signing. Not sure but I believe I vaguely remember the gateway needs to be signed as well.
-
Thanks both for the replies.
Yes the gateway is signed, it has all been working for years, but I have recently become aware of the reboots (turns out it's been happening all along) but the code recovers gracefully. I simply wanted to determine if the signing is "at fault".
I have read the above referenced page, and links therof. My question is for clarification of this sentance."When not set, any node that has presented themselves as a node that require signatures or whitelisting, will be permanently remembered as doing so at the receiver until EEPROM is cleared or the receiver is reconfigured with this flag set or has signing disabled alltogether."
I suppose my question really becomes, Which EEPROM? The node (how I origionally thought of it) or the Gateway, or both? I suspect it may well be both, but I thought somebody would know definatively.
-
Not sure if you need to erase the eeprom from the node. As the key is stored within the encryption chip when you sign it - this is somewhat of a guess, based upon my understanding of signing.
Erasing the GW eeprom wouldn't be a bad idea. Because that's where the administration probably is stored. As far as I know other nodes are not influenced event when they are repeaters. As repeaters don't even know wetter the other nodes are signed.Hope my 50 cents help out.