Files
vectorcraft/crates/engine
dotCooCoo 8459c52a8c MCP: confined exports refuse native files that name a linked JavaScript file outside the read roots
Under --automation-read-root, a document that links a JavaScript file
outside the read roots could still be written by a confined caller to
any output that carries the native document, and that document holds
the stored path. SVG and SVGZ output was already refused. This change
applies the same control to every output that carries the native
document, and they now return the same error, "a linked JavaScript file
is outside the read roots", without the path:

- document.serialize, document.export, document.exportSelection and
  document.exportEps for vectorcraft, template, EPS, .ai and .ait files
  (not a legacy version 7 .ai file, a .ai file of some of the
  artboards, or one of the art's bounds)
- PDF with Preserve Editing on, as its preset, standard and options
  leave it, when it holds every artboard, including document.exportPdf
- document.save, file.saveAs and file.saveAsTemplate
- document.exportForScreens and assets.export, checked with the
  artboards each file is written with
- file.exportAs in the app
- file.package, before the folder is made, including when a linked
  native document, or the native document a linked PDF, .ai or EPS
  file carries, links such a file

Outputs that do not carry the native document, unconfined callers and
linked files inside the read roots are written as before.
2026-11-14 05:21:40 -08:00
..