Posts made by Kestutis Mockus

Well to check if password is changed, verify message could be sent with new encryption, if no replay - send new password change command again. For password sending in OTA - new password could encrypted with predefined encryption key which would be safely saved in atcha and defined uniquely by each developer.
It is just my thoughts, as I understand it cannot be accomplished easily without modifining core files and private modificated files would be overwriten by updates.
Will waot for future updates if something similiar will be developed.
Thanks and sorry for english

Sorry for delay. I mean send password not in FOTA but as separate command. In that case gateway should communicate with signed and not signed password nodes. From insecure node only limited commands would be accepted by the gateway, so no hacks would be available like door opening and etc.
The controller would initiate process of changing or assigning password.
So if password gets leaked or node stolen, you would need only initiate password change command in controller without re flashing all nodes with new password.
I know it maybe a security issue, but it would be a lot easier to use same node firmware version for multiple signed passwords.

Hi all.

I was wondering if there is a possibility to remotely assign password to node from controller, that is used for signing?
Currently you have to hardcode your password in gateway and nodes if you want to do signing. I think it would be really cool if secret password assigning could be achieved remotely without needing to edit sketch file and node would be easily reused in other secured network, by resetting its eeprom data with custom reset button.
Also you could change password in all nodes remotely if it gots leaked somehow without reprogramming each node separately .