diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-09-10 17:30:00 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-09-10 17:30:00 +0200 |
| commit | efc93c187dba9027292b51ff0e9caa29349c953e (patch) | |
| tree | 9e5a397a6ddb5cd52279861750f70357dfb1047a /packages/meshbay-node/tests | |
| parent | 4753c67816c774323e3ab4efc76d3259e8ded40d (diff) | |
| download | meshbay-efc93c187dba9027292b51ff0e9caa29349c953e.tar.gz | |
refactor(node): QUIC does not relay chat it cannot check
The QUIC handler stored `payload` as it arrived and broadcast it: no envelope,
no signature check, no `device_hello` to check one against. A message reaching
a group's archive that way is a plaintext row in an encrypted history, and it
would be indistinguishable from one somebody actually wrote.
Removed rather than gated. The transport implements neither the per-device
sealing nor the device identification the WebRTC path requires, so refusing
here would mean maintaining a second, weaker set of rules for a transport with
no client; an unimplemented type is logged and dropped, like every other message
this transport does not have.
The comment on the peer registry loses its chat fan-out aside for the same
reason.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AsoWC3GmhNdwVFomW3QjH3
Diffstat (limited to 'packages/meshbay-node/tests')
0 files changed, 0 insertions, 0 deletions