summaryrefslogtreecommitdiffstats
path: root/cmd/nymdrop-source
diff options
context:
space:
mode:
authorGab Virebent <gabriel1@virebent.art>2026-07-11 13:37:23 +0200
committerGab Virebent <gabriel1@virebent.art>2026-07-11 13:37:23 +0200
commitfbd064eb06f93652925e4b4f0061408d41024021 (patch)
treeb3d4f42851d1b2c413a15f8ec7dea9a51659e494 /cmd/nymdrop-source
parenteae435a87aaf60c1da17a9df40c6277eb92458c7 (diff)
downloadnymdrop-fbd064eb06f93652925e4b4f0061408d41024021.tar.gz
nymdrop-fbd064eb06f93652925e4b4f0061408d41024021.tar.xz
nymdrop-fbd064eb06f93652925e4b4f0061408d41024021.zip
Switch Nym WS transport to nym-client's binary protocol, drop second base64 layer
Client.Send now speaks nym-client's native binary websocket protocol (tag || recipient || conn_id || data_len || data) instead of wrapping the ciphertext in a JSON text message, which required base64-encoding it a second time on top of the browser's own base64 layer. The reader's self-address query also switched to the binary protocol: nym-client picks text-vs-binary for every later "received" push based on the format of the last request seen on a connection, so leaving the reader in JSON/text mode would have made nym-client run a lossy UTF-8 conversion over the now-unencoded binary payload, corrupting it. Fixed the binary Received-frame parsing along the way (previous code assumed a fixed 16-byte tag with no length prefix, which never matched the real protocol and was never exercised while the connection stayed text-mode). Verified end-to-end against the real embedded nym-client 1.1.76 binary, with the exact wire format cross-checked against upstream nym source at the pinned build commit.
Diffstat (limited to 'cmd/nymdrop-source')
0 files changed, 0 insertions, 0 deletions