Hi,
I am wondering whether the developer portal decrypt the lora payload or it is expected to be done at the application server?
Following this https://zakelijkforum.kpn.com/lora-forum-16/lorawan-security-encryption-and-authentication-10957 I think that my application server has to do it since the dev portal doesn't do it, could ou confirme it?
Thanks in advance
Hi @JCL ,
It is correct that the decryption of the payload should be done at your application server 😁
It is correct that the decryption of the payload should be done at your application server 😁
It is correct that the decryption of the payload should be done at your application server 😁
Then if I used node-red and I understand well, first I have to get the LoraWAN payload from the DevPortal performing a SHA256 Check onto it, thus I will get the LoraWAN payload encrypted with the AppSKey. Secondly, I wil have to decryot that payload with the AppSKey in order to get my real payload.
Is this reasoning correct?
Thanks!
Hi @JCL ,
I saw that you also placed this question under the topic LoRaWAN Security: Encryption and Authentication . Meanwhile my colleague Lennart Nordin has also given an answer to that. Have you seen this answer?
I saw that you also placed this question under the topic LoRaWAN Security: Encryption and Authentication . Meanwhile my colleague Lennart Nordin has also given an answer to that. Have you seen this answer?
In the Developer portal documentation it states that:
"Messages are forwarded unencrypted. The developer portal already decrypts the LoRa data using the randomly generated AppSKey. No further decryption is necessary. In the Commercial LoRa Service end-to-end encryption is supported.
All payloads are hexadecimal however, meaning they have to be decoded in some way to be used in applications. The decoding scheme depends solely on what the device manufacturer programmed in your device."
Does this answer your question?
I saw that you also placed this question under the topic LoRaWAN Security: Encryption and Authentication . Meanwhile my colleague Lennart Nordin has also given an answer to that. Have you seen this answer?
In the Developer portal documentation it states that:
"Messages are forwarded unencrypted. The developer portal already decrypts the LoRa data using the randomly generated AppSKey. No further decryption is necessary. In the Commercial LoRa Service end-to-end encryption is supported.
All payloads are hexadecimal however, meaning they have to be decoded in some way to be used in applications. The decoding scheme depends solely on what the device manufacturer programmed in your device."
Does this answer your question?
Thanks
When the forwarded payload hits my backend, the payload that I am getting is this
\"payload_hex\":\"940adfc976bffbf80dfe452c615a0410465d3549651967260c948e03\"
\"value\":\"940adfc976bffbf80dfe452c615a0410465d3549651967260c948e03\"
which seems encrypted to me becuase I don't send that data from my device.
Kind regards
Reageer
Meld je aan
Heb je al een account? Inloggen
Welkom
Nog geen account? Maak een account aan
Inloggen of registreren met sociaal netwerk
Inloggen met Facebook Login with LinkedInof
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.