Whitelist not wirking from sensor to gateway

[karelsmits]

This is my node code regarding signing:

#define MY_NODE_ID 5
 
#define MY_DEBUG //!< Enable debug prints to serial monitor
#define MY_DEBUG_VERBOSE_SIGNING //!< Enable signing related debug prints to serial monitor
#define MY_NODE_LOCK_FEATURE //!< Enable lockdown of node if suspicious activity is detected

// Enable and select radio type attached
#define MY_RADIO_NRF24 //!< NRF24L01 radio driver
//#define MY_RADIO_RFM69 //!< RFM69 radio driver

// Select soft/hardware signing method
#define MY_SIGNING_SOFT //!< Software signing
//#define MY_SIGNING_ATSHA204 //!< Hardware signing using ATSHA204A

// Enable node whitelisting
//#define MY_SIGNING_NODE_WHITELISTING {{.nodeId = GATEWAY_ADDRESS,.serial = {0x09,0x08,0x07,0x06,0x05,0x04,0x03,0x02,0x01}}}
// Enable this if you want destination node to sign all messages sent to this node.
//#define MY_SIGNING_REQUEST_SIGNATURES


// SETTINGS FOR MY_SIGNING_SOFT
#define MY_SIGNING_SOFT_RANDOMSEED_PIN A5 //!< Unconnected analog pin for random seed

// SETTINGS FOR MY_SIGNING_ATSHA204
#define MY_SIGNING_ATSHA204_PIN 17 //!< A3 - pin where ATSHA204 is attached

[Anticimex]

@karelsmits on beta with all debugging enabled and signing, code gets so large that the stack becomes too small. This can cause "cheap" gateways to crash and reboot. I am guessing you run some atmga328p based gw right?
Try to disable at least the verbose debug, possible all debug on the GW and it should run better.

[karelsmits]

Dear Anticimex,
Thank you so much for helping out.
This is what I had to do to solve this:
I used the development edition of mysensors, I had to disable debugging, because indeed I use cheap boards. Then I also had to use the personalizer from the development and not change anything in the config file.
I just have 1 more question for now. Everything is secured for now, the only thing which isn’t, according to my understanding, is that any controller could communicate with my Ethernet gateway. Of course I could specify the ip address of the controller I want to use in the Ethernet gateway ino file configurations, but an ip address could easily be “doubled” either by causing an ip-conflict, or just plugging out or somehow disabling my controller.
So, the question is; how can a code or something be specified, besides the ipaddress, in the gateway. And with that security code only, the gateway will be able to be controlled by a controller device like eg Domoticz.
.Thank you.

[Anticimex]

@karelsmits great that you got it up and running at last!
Regarding gateway security, the security of the library is limited to the OTA parts. It is assumed that you connect your gateway to a secure environment. Your LAN or USB host. If criminals can access your LAN you have a bigger problem than somebody spoofing your controller

[karelsmits]

when it says in the gateway code:

// The MAC address can be anything you want but should be unique on your network.
// Newer boards have a MAC address printed on the underside of the PCB, which you can (optionally) use.
// Note that most of the Ardunio examples use  "DEAD BEEF FEED" for the MAC address.
//#define MY_MAC_ADDRESS 0xDE, 0xAD, 0xBE, 0xEF, 0xFE, 0xED

which mac address is this referring to? the gateway? the controller?
And what happens if it doesn't match?

thanks

[Anticimex]

@karelsmits this is rather off topic. I suggest you move that question to a different thread as it has no relation to signing or security.