Encryption with RFM69 [solved]

[Les]

@anticimex Thanks for the tips. I did review those pages and based on that it seems that #define MY_SECURITY_SIMPLE_PASSWD "yourpassword" is all that would be required unless you would like to personalize. I would like to keep it simple though.

[Anticimex]

@les right, but you also write that you were interested in encryption and not signing, so it is not the correct flag in that case. And also, note that you need the same flag on all nodes and gw if you use one that enable encryption.

[Les]

@anticimex according to the documentation

MY_SECURITY_SIMPLE_PASSWD Enables security (signing and encryption) without the need for personalization

So the connection should be encrypted and signed without anything else (other than putting the same define statement on all nodes with the same password).

[Anticimex]

@les correct.
Have you checked the troubleshooting section in the docs regarding signibg issues? There is also a more verbose debug flag available.

[Les]

@anticimex said in Encryption with RFM69:

roubleshooting section in the docs regarding signibg iss

I see that now, will give it a shot.

[kimot]

#define MY_RFM69_ENABLE_ENCRYPTION

All nodes and gateway must have this enabled, and all must be personalized with the same AES key.
You need a helper-sketch specifically for this purpose

• SecurityPersonalizer.ino

[Les]

@kimot Ok, thanks for that info, I thought with MY_SECURITY_SIMPLE_PASSWD you didn't need to personalize. If I'm reading the instruction properly flash securitypersonal.ino to device, copy out the key and then paste to all nodes. Which sounds simple. Have I missed anything?

[Anticimex]

@les correct, no personalization needed. But with that flag, all nodes in your network need to share it. And memory requirements increase significantly so pay attention to the compiler log regarding warnings on memory use.

[Les]

I added the following to the top of my code:
#define MY_DEBUG
#define MY_DEBUG_VERBOSE_SIGNING
#define MY_SECURITY_SIMPLE_PASSWD "testpass"

And it works now....not sure if having the Security above the radio information helped, but it does work now :)

[Anticimex]

@les great! We'll, the debug flags should not help getting things to work, only provide additional information if it doesn't.
All configuration flags need to be placed prior to any header include directives. Else they will have no effect.
Anyway, glad it worked out in the end.