D04-MT: Yes
Rationale
The native Linux role already selected in D01 and C06 supplies a bounded Yes. An ordinary user with preauthorized access to a real CH341 LoRa radio can run a private meshtasticd context with its own configuration and VFS (-c and -d), explicit logical MAC, keys and peer records. NodeDB generates a new key pair inside that context, installs its private key into CryptoEngine, and derives the node number from the public key in createNewIdentity. Router assigns that local node number to originated packets. The logical MAC setting supplies firmware metadata; it does not change a Linux interface address. Creating another user-owned context therefore does not require a new host address, route, prefix or per-identity administrative allocation. Independently owned contexts, rather than serial clients sharing one firmware owner record, are the witness.
Assessment method
Source-level identity/privilege boundary and consistency with existing D01/C06 witnesses; no execution
Source context
Pinned native firmware identity and radio paths; official per-context VFS and device-permission documentation
Outstanding qualification
Use the existing headless native configuration, no ambient capabilities, nonprivileged or disabled local servers, independently owned files and already provisioned device permissions. Keep the selected private-channel and STRICT policies; peers still decide whether to accept the new key. Contexts can be used sequentially on an exclusively assigned radio; concurrent contexts require separately available authorized radios, with unique CH341 device serials where applicable. This does not claim multiplexed identities inside one shared embedded node, simultaneous sharing of one USB device, seamless identity rotation or unlimited radio resources. The single-owner firmware observation remains true but no longer blocks the allowed separate-instance witness. Source/documentary finding, not a new multiuser permission trace or RF experiment.
Public sources
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/NodeDB.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/Router.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/platform/portduino/PortduinoGlue.cpp
- https://meshtastic.org/docs/meshtasticd/usage/
- https://meshtastic.org/docs/meshtasticd/hardware/
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round371-sources.json