docs(docs): R4.9 verifier and security follow-ups: §6 rows 19 (J2 device run, blocking before merge) and 20 (WebKit worker error trace); port 4173 in the exposure table as an owner-opened recette rule; serve.mjs post-bind check typed from the address; report-compare comment names the residual race
This commit is contained in:
1 parent
854d988c07
commit
49b812b9b4
6 files changed
+21
-11
No files matched your search
@@ -21,6 +21,9 @@ Two surfaces, both on the DEV origin (`scripts/dev-env.sh`,
|
||||
2. The production build behind the DEPLOY CSP (what the proofs ran):
|
||||
`pnpm build:preview` then
|
||||
`. scripts/dev-env.sh && node scripts/browser/serve.mjs --host "$FAUNOSTEO_DEV_HOST" --port 4173` (the server refuses an empty or unspecified address),
|
||||
reachable from the devices only once the owner opened port 4173 to the
|
||||
private subnet for the session (`ENVIRONMENTS.md` §3, the 4173 row:
|
||||
one `ufw allow` rule, deleted afterwards),
|
||||
`http://<FAUNOSTEO_DEV_HOST>:4173`. Static files, the nginx SPA fallback,
|
||||
the DEPLOY `Content-Security-Policy` with `'wasm-unsafe-eval'` on every
|
||||
response. `--csp without` serves the same build without the keyword (the
|
||||
|
||||
Reference in new issue
Block a user