Wrong instructions on gateway for personalizer?

[pepson]

But for what is signing and for what is encryption ?

[Anticimex]

@pepson Could you rephrase that question please? I don't understand it. Have you read the documentation I linked to?

[gohan]

@pepson said in Wrong instructions on gateway for personalizer?:

But how use it on my Gateway on RPi3 with radio RFM69HW ? I think about point number 1... Because --my-rfm69-encryption-enable not reconized......

You need to uncomment the //#define MY_RFM69_ENABLE_ENCRYPTION in myconfig.h on the RPI and recompile the gw.

[Anticimex]

@gohan I suggest you avoid hacking in MyConfig.h. Just define what you need in the sketch prior to including MyConfig.h instead. MyConfig.h provide default values. Most of these are designed to be overridden. That way, you only need to change your ino file and not mess with the library code. If you have multiple sketches using the same library they will inherit anything you hack on the common code (like MyConfig.h) and that is not necessarily what you want.

[Anticimex]

@gohan furthermore, for rPi, configuration is handled with the configure tool. Not MyConfig.h.

[gohan]

what is then the rfm69 encryption command? I didn't find it and the one I set in myconfig actually does the job.

[Anticimex]

@gohan well, that is indeed strange because the entire feature is not existing (see here: https://github.com/mysensors/MySensors/pull/1054)
Please don't give incorrect advice on security topics.
Where have you found the flag you mention?

Edit: wrong radio and pr, I mean this: https://github.com/mysensors/MySensors/pull/1056

[gohan]

On line 753 of myconfig.h

[Anticimex]

@gohan see my edit

[gohan]

I don't understand what you want me to do

[Anticimex]

@gohan don't suggest people hack in MyConfig.h because it's the wrong thing to do.