RNSpure rnodeconf is broken without cryptography module

[ctand]

@markqvist @jacobeva

Like the title explains, when using RNSpure, rnodeconf is broken without the cryptography module which is the whole point of using RNSpure.

How would we feel about pycryptodome as an option? I've run out of options trying to get the cryptography module working on the LuckFox Pico Mini due to UClibc buildroot issues. RNSd and LXMd work via RNSpure which I'm very happy with but without the ability to configure the RNode via rnodeconf, I'm a little stuck. RNSpure could implement the primitives required to finish the job but it seems like a big lift. Let me know what you think.

[cobraPA]

Well, you can always setup RNode on another system... there is no requirement to configure it on your smaller portable/remote system?

[ctand]

This is about maintenance though. This is going to be mounted on a tower on a mountain. It's not something easy to access.

I ideally one would be able to send the firmware to the linux host using rncp and then issue the update command using rnx to run a script that updates the firmware and any software really with some checks to make sure things can be rolled back if they fail.

I think rnodeconf requiring the python cryptography module in the rnspure release is more of an oversight than anything. The included cryptographic primitives exist for this purpose but they just aren't implemented in the tool because the tool was written before rnspure.

[cobraPA]

hmm, yeah, that is a special case... I'd be worried that you may need to power cycle or reboot the rnode when running rnodeconf remote. Do you have a way to do that?

[ctand]

RNSpure should just work with all the tools it includes so this is beside the point. I don't think this is a special case. For LoRa to work well, nodes need to be sited similarly.

To answer your question, yes, I can hard reboot the RNode via the enable pin on the buck I'm using for my 3v rail.