F15-MT: Yes
Rationale
The selected firmware bounds fromRadioQueue to four packets; overflow discards and releases the oldest. Before stateful routing filters and local dispatch, passesRoutingAuthGate rejects signature-policy failures. STRICT rejects unsigned non-PKI packets and invalid signatures. This combines bounded waiting-state with rejection before retry/history updates and decoded local delivery.
Assessment method
Primary documentation and pinned source review; no runtime experiment
Source context
Pinned Meshtastic Router receive queue and signature-policy gate
Outstanding qualification
Credit the receive queue, not total memory: Portduino uses a dynamic packet pool. Decryption, signature verification, key lookup and bootstrap checks precede rejection and cost CPU. PKI packets follow their authenticated-decryption path without requiring an additional signature. First-contact NodeInfo can bootstrap trust; STRICT is not an authorized-person whitelist. Ordinary CLIENT/ALL still relays eligible opaque traffic, including unknown channels; that path is not claimed to reject every unauthorized sender. Do not substitute the separate KNOWN_ONLY witness. Flooding can displace legitimate queued packets and saturate processing or airtime. No fairness, service-floor, whole-device memory bound or runtime result is asserted.
Public sources
Editorial evidence references
The following identifiers refer to research records not included in this public package; they are not public links.
- round546.html
- round546-sources.json