F16-MT: Yes
Rationale
Select a headless CLIENT with KNOWN_ONLY and STRICT, a clean locally provisioned database containing only authorized User records and confirmed full public keys, trusted local serial administration, no remote administrative grants to ordinary peers, and store-forward disabled. KNOWN_ONLY rejects an unknown sender before decrypt/first-contact learning; STRICT then requires a valid signature or authenticated PKI payload for admitted records. Thus a known node number alone is insufficient: an impostor must pass the retained full-key check. For bounded revocation, persist the revoked node number in ignore_incoming while retaining its key binding, verify saved policy, then restart before declaring cutover. Ignore checks precede admission; restart discards volatile radio, deferred-dispatch and phone queues, and surviving authorized records remain usable. A new sender number still fails KNOWN_ONLY. This uses native controls and the restart allowed by F16, not an external firewall or added application authentication. It is not the default ALL policy, zero-interruption revocation, a generic arbitrary-NodeDB allowlist, or revocation of data already delivered.
Assessment method
Pinned control-flow and bounded administrative composition analysis; no firmware execution
Source context
Meshtastic 8e6a88d Router, NodeDB, MeshService and AdminModule
Outstanding qualification
Execute with two authorized peers and one unlisted peer on the pinned headless build. Verify full-key provisioning and effective KNOWN_ONLY/STRICT; test forged known numbers, changed keys, unknown self-signed NodeInfo and valid authorized payload. Queue a revoked-peer packet, persist/read back ignore_incoming, restart, then prove no old queued or new revoked payload is delivered while the surviving peer succeeds. Exclude display/message-history modules and remote administration from this witness; store-forward stays off. Failed persistence or incomplete restart is not a completed cutover. No runtime qualification performed.
Public sources
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/Router.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/NodeDB.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/mesh/MeshService.cpp
- https://github.com/meshtastic/firmware/blob/8e6a88d06f44cad26f1e8d7cd402939ccacb9b4c/src/modules/AdminModule.cpp
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round122-sources.json