What I find funny here is that the complete data packet is not encrypted!
It seems to me, that the data packet is split up into distinct parts visible to the hacker.
I guess the designers don't understand the encryption fully.
QK0ZAS is static.
YAFwAB these seem to be incrementing.
These two fields seem to be predictive.
Not good when I can use the second board to clone packets.
If I send the same type of data, how will the end user know which is his under LoRaWAN?
How does LoRaWAN do authentication on data packets and nodes?
The SoDaQ ExploRer board with SoC LoRaWAN does not care its a clone of my other kit.
Why would a protocol doing MAC not care about cloning?
Other security issues.
IoT uses small data payloads.
You see when payloads go down to 64 bits.
We can start to look at cracking this, I think.
LoRaWAN is a failing protocol due to poor design.
It has to HIDE secrets in IT systems.
Security Via Obscurity
Hows that working out for the world?