C06-MT: No
Rationale
The selected Meshtastic radio PacketHeader contains the final to/from NodeNum fields separately from the protected payload and the next_hop/relay_node fields. A radio observer can associate the sender and destination NodeIDs without decrypting the direct-message payload.
Assessment method
Primary documentary reassessment; no runtime experiment
Source context
RFC routing/discovery mechanisms and pinned Meshtastic header
Outstanding qualification
PKI payload encryption, private channel keys and strict signatures remain selected, but do not hide these header fields. Distinct provisioned identities between contexts do not conceal the pair within a communication. This identifies radio endpoints, not necessarily legal persons; no timing inference or fabricated decryption is required.
Public sources
- https://raw.githubusercontent.com/meshtastic/firmware/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/RadioInterface.h
- https://meshtastic.org/docs/overview/mesh-algo/
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round491.html
- round491-sources.json