New answers tagged

0

You can try some workflows provided by OAUTH providers. Essentially, you place some credentials in the machine and use them to procure a token. The token is then sent along with your requests to your server. Both the RASPI and your REST service use the provider as a reference for the validation of the requestor. If you need more information, you can refer to ...


1

There is a simple way to prevent your users using your REST API from outside their RPI. It would work in the following way: You protect the file system of the RPI by a root password that is not shared with the user. The filesystem must be encrypted too. Instead of assigning an access token to a user, you assign a security key. The user puts the security key ...


2

Actually even in OTA (using Join) the LoRaWAN spec separates the network session key (used by the network server to verify checksums and potentially de-ambiguate colliding short DevAddr addresses into their unique devEUIs), and the payload encrypting session key (AppSKey). It is one of its key innovations compared to other MAC layers like 802.15.4. The trick ...


0

I'd like for you to consider these points that arise from your questions. Are you wanting to classify the entire device or are you wanting to classify the data ? i.e, Is it possible now (or in the foreseeable future) for a single device to send up data of different classifications ? What threats do you want to protect against ? This will determine your ...


Top 50 recent answers are included