add secure_packet_v1 for secure concentrators #194
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abhay
reviewed
Oct 13, 2022
src/service/poc_lora.proto
Outdated
| optional uint32 vacc = 5; | ||
| } | ||
|
|
||
| // Duration since the GPS epoc (0h 6-Jan-1980) |
There was a problem hiding this comment.
removed comments about the well known type... better to look at this proposed guideline #208
devilish66694
approved these changes
Jun 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Secure LoRaWAN Concentrator cards sign RX packets in hardware using unique ED25519 key. The signature consists of the actual packet data plus metadata (frequency, datarate, snr, rssi, tmst, and GPS time/location). All this data must be available to validate the signature. This PR proposes adding an optional
secure_packet_v1message type to thelora_beacon_report_req_v1