2025-08-10 16:19 UTC
The core issue to the above PKI poisoning attack is that NO core parts of meshtastics protocol is signed.
The user profile transmits the public key and there is no way to verify any of the information in it was even sent by that included public key 🙄
Nothing is signed and simply setting someone else's MAC address in the unencrypted header makes you that user.
Replies (2)
-
@nullagent@partyon.xyz 2025-08-10 16:33
The scale of meshtastics avoidance of building security into the design is pretty epic. It allows for the formation of an entire mesh just for MITMing it. This ONE liner here in the PKI attack means that once a node gets poisoned the key we created is based on the MAC so -anyone- who knows your MAC can read your MITM'd traffic. When attackers run mesh marauder against the DEFCON 33 firmware they are all working together. Anyone in range can read the MITM'd DMs. https://github.com/datapartyjs/meshmarauder/blob/channel-chat/src/lorapipe-raw-packet.mjs#L191-L193
-
@mhoye@mastodon.social 2025-08-10 16:27
@nullagent@partyon.xyz Excuse me _what what_!?!