diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-09-01 18:56:01 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-09-01 18:56:01 +0200 |
| commit | 9f7698340e5148f8f247fe0d70a57f7f37f1f72d (patch) | |
| tree | 33a751788fc8c877eb97be2cea7782800f3383af /packages/meshbay-node/src/meshbay_node/transport | |
| parent | 73a119cbc7641b5f0005d0ce8bc4c7b0b7ae6a6e (diff) | |
| download | meshbay-9f7698340e5148f8f247fe0d70a57f7f37f1f72d.tar.gz | |
feat(node): [node] quic_enabled flag, off by default
The QUIC MNP listener was started unconditionally whenever aioquic was
importable — but nothing speaks QUIC: the browser and desktop clients
use WebRTC, QuicChunkClient has no production caller, and the hub-less
`group://` sidecar (D9) is unbuilt. So on every node it was an open
UDP port with no client and no working NAT traversal (`punch_nat()`
is a direct-connection helper, not a traversal stack).
daemon startup now gates QuicChunkServer on
`self._config.node.quic_enabled` (default False; `MESHBAY_QUIC_ENABLED`
overrides). The generated node.toml templates (config.py, the CLI, the
desktop client) carry the line, commented for what it is.
Removes the exposure the third review's M2 lives on until a QUIC
client exists; the parity fix for the handlers themselves is the next
commit.
Third security review, finding M2 (mitigation).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011pG75yGK3NthNfyjH74omG
Diffstat (limited to 'packages/meshbay-node/src/meshbay_node/transport')
0 files changed, 0 insertions, 0 deletions