diff options
| author | Gab Virebent <gabriel1@virebent.art> | 2026-07-03 15:51:07 +0200 |
|---|---|---|
| committer | Gab Virebent <gabriel1@virebent.art> | 2026-07-03 15:51:07 +0200 |
| commit | 4fd6b4fefa7243f68fae7e24df3da46ee1a8e356 (patch) | |
| tree | 45d41d62c2b5ddb0a4a85e4a429597c8d31d8d89 /static/index.html | |
| parent | 25fb52dc5c587acca2f4457d5c6f7b8032b7829c (diff) | |
| download | nymdrop-4fd6b4fefa7243f68fae7e24df3da46ee1a8e356.tar.gz nymdrop-4fd6b4fefa7243f68fae7e24df3da46ee1a8e356.tar.xz nymdrop-4fd6b4fefa7243f68fae7e24df3da46ee1a8e356.zip | |
Fix payload cap: double base64 inflation broke files near the old 10MB limit
The old 10MB cap was checked against the wire body, but two base64 layers
sit between the raw file and that body: crypto.js base64-encodes the file
before AEAD encryption, then nym.Client.Send base64-encodes the ciphertext
again to embed it in the JSON sent to the local nym-client over its control
WebSocket. A file at exactly the old cap produced a wire body just over the
limit after the first layer, and would have blown nym-client's own hardcoded
16MB WebSocket message limit after the second, surfacing as an opaque 500.
Lower the wire-body cap to 11MB, which keeps the second base64 layer with
real margin under nym-client's 16MB ceiling. Effective safe raw file size
is now roughly 8MB, not 10MB.
Reported by Ch1ffr3punk on nym.forum, reproduced with an exact 10MB file.
Diffstat (limited to 'static/index.html')
0 files changed, 0 insertions, 0 deletions
