examples: lora: Store the LoRa keys in the K/V store #461
Conversation
alistair23
force-pushed
the
alistair/lora-keys
branch
2 times, most recently
from
9ce20db to
d49f6e6
Compare
|
Sorry things have been slow in libtock-c. Life is letting up a bit and I should have more time to attend to stuff here in a more timely manner moving forward. Ideally, we can get #456 in next week and then can look at this one. [btw, is it feasible to have as a merge base target PR#456, i.e. |
alistair23
force-pushed
the
alistair/lora-keys
branch
from
d49f6e6 to
4ba5a65
Compare
|
This is rebased and ready to go.
Not that I know of. Each one is cleaning rebased on the previous PR, so it's easy to track the changes in git, but I have no idea how to do that in GitHub |
|
Sorry #456 took so long; hopefully this is a relatively painless rebase of the new commits |
alistair23
force-pushed
the
alistair/lora-keys
branch
2 times, most recently
from
dee7168 to
cec2f05
Compare
|
This is rebased |
This modifies the LoRaWAN example to use keys set in Tock's K/V store. The `lorawan-set-keys` application is added to set keys, which can then be used over and over again by the LoRaWAN transmit application. Signed-off-by: Alistair Francis <[email protected]>
alistair23
force-pushed
the
alistair/lora-keys
branch
from
cec2f05 to
6a5a9df
Compare
|
Ping! |
This builds on top of #456, which builds on top of #432 to store the LoRaWAN keys in K/V storage.
This modifies the LoRaWAN example to use keys set in Tock's K/V store.
The
lorawan-set-keysapplication is added to set keys, which can thenbe used over and over again by the LoRaWAN transmit application.
This means that once a board has been flashed the LoRaWAN application can easily be changed without worrying about keys. It also opens up the possibility of storing the keys from a side application (such as a BLE interface).