security: publish RFC 9116 reporting metadata #234
No reviewers
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
key-store/key.store!234
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "security/security-txt-rfc9116"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
security.txtfile forkey.storeandlately.org, expiring2027-02-28T00:00:00Z/.well-known/*paths from falling into either SPA while preserving exact routes and the WKD treeLatelySecretStoresource in the filtered wasm input; without this existing omission,nix build .#web-containerfailed before reaching the web derivationRedmine: https://todo.key.store/issues/7
First-work child: https://todo.key.store/issues/22
Renewal reminder (due 2027-01-29): https://todo.key.store/issues/8
Proposed policy wording for review
key.storeand its subdomains;lately.org; and official key.store/Lately web, Apple-platform, Android, Linux, Windows, KaiOS, and browser-extension surfaces built and distributed from this repository.The requested main-branch policy URL,
https://git.key.store/key-store/key.store/src/branch/main/SECURITY.md, returned anonymous HTTP 404 before this PR. The branch version loads anonymously, but I did not add aPolicy:field because the exact main URL cannot be relied on until merge.Validation
bash bazel/web/runner.sh lint-build— passed after rebasing onto current mainnix build --accept-flake-config .#web-container— passed after rebasing onto current main--format-only— passed, proving the Nix-mode check has no clock dependencyLocal nginx curl matrix
Generated from the built container's
nginx.confand built site withHostheaders:Founder sign-off, recorded by Codex at Conrad’s explicit request on 2026-09-13: this first-work-wave change is approved. Resolve any conflicts and satisfy the required checks before merging. This records the founder’s approval; it does not assert that failing checks have passed.
56f418515abee03cee1bRebased onto current main (
6bee2614). One conflict in flake.nix resolved: kept the KSE-0195 E1 comment; dropped my one-line LatelySecretStore addition as already present upstream. Patch vs new base is the same 5 files. Verified locally: node Web/scripts/check-security-txt.mjs --format-only passes. Ready for independent review; I cannot approve my own change.bee03cee1b0aee8c5ffdRebased onto current main (
a8d14c50): single commit0aee8c5f, signed, no conflicts. Validation:node Web/scripts/check-security-txt.mjs Web/public/.well-known/security.txt-> ok (full mode, Expires 2027-02-28); diff secret-scan clean (only policy prose mentions). Ready for independent review — I will not approve my own PR.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.