docs(docs): J1 device run recorded as reported (no failure; devices and measures pending confirmation)

This commit is contained in:
bchanot committed 2026-10-18 21:18:34 +02:00
1 parent d2647505b0
commit 769544a1e8
3 files changed
+40 -18

No files matched your search

+13 -5
View File
@@ -88,11 +88,19 @@ hides its `/Keywords`, so a stripped attachment on such a file reads as
- Option A merged and the CLI on the scanner; no `PDFDocument.load` on any
untrusted input in the browser.
- A real-browser test of the inflate bound (Chromium, Firefox, Safari): the
vitest suite runs in Node and cannot see a browser inflater's read-ahead.
The audit of 60ee712 measured +2.2 GB RSS in Chromium on a 4 MB / 4 GiB
bomb before the inflater was fed in 16 KiB slices (+215 MB after); that
measurement is manual until a browser runner exists.
- Done at R4 (2026-10-18, `docs/development/RUST.md` §10.3 to §10.5): the
reader runs in Rust inside a disposable worker; the inflate bound and the
hostile classes were measured in Chromium 156, Firefox 157 and WebKit 27.2
(headless): a 16 MiB + 1 bomb costs 63 MiB of linear memory and is
refused, 32 bombs 68, a 16 MiB token-dense document 16 MiB under the
400,000-value cap (784 MiB with it off), the 1 GiB module ceiling traps;
the application build answers the same outcome and message as the
TypeScript reader on 666 of 678 (file, engine) pairs, the other 12 being
the four declared hostile files. Device run (J1, `R4_J1.md`): the owner
reports the functional checks executed on 2026-10-18 with no failure;
the device list, versions, scenario coverage, timings and memory
observations are recorded in `R4_J1_RESULTS.md` as they are confirmed.
The gate below stays open: imports are not offered to external users.
- Done: the candidate CPU/byte budget on the scanner: one 16 MiB budget of
retained and parsed content shared by every candidate (a cancelled
inflation is not charged, so up to 32 oversized streams may each cost one