Repository navigation
Conversation
…d scope Add a dedicated Security Model page covering the trust boundaries, temporary-file and cache handling, password-protection limits, resource isolation, and reporting responsibilities. Both the English and zh-cn pages are added and registered in the community sidebar. The page states explicitly that password protection covers completed XLSX output only, that intermediate plaintext may remain in temporary files and process memory, that the URL image fetch policy is process-wide and denies remote fetching by default, and that replacing the XML parser factory changes the hardening that is applied. Cross-link the page from the Security page and from the password document, and correct the password notes, which previously implied full-content encryption for every format. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
I noticed that only some of the H2 headings explicitly define custom anchor IDs (such as Just wondering, is this intentional for specific deep-linking/referencing needs, or would it be better to standardize the format across the entire document? |
|
Thanks @bengbengbalabalabeng. These explicit IDs serve the cross-page links from the English and Chinese Password Protection pages: Keeping the same IDs in both languages makes those links stable when headings are translated or reworded. The remaining sections use Docusaurus-generated IDs, which still support navigation and linking. I've kept the existing anchors unchanged because only these three sections currently need shared, stable targets for those references. |
Purpose of the pull request
Document the security model of Apache Fesod (Incubating) so users understand its trust boundaries, security guarantees, and application and deployment responsibilities.
What's changed?
Validation includes Markdown linting, English and Chinese production builds, and checks of generated navigation links and section anchors using the existing local dependencies. No Java runtime behavior is changed.
Checklist