Both1.0.1 release candidates passed acceptance and Azure login but stopped before signing because of the shared inline PowerShell wrapper. Pin the corrected, personally approved standards1.1.2 builder at083d903. Preserve failed tags; use new1.0.2 stable/dev refs, prepare direct EXE/ZIP download links, correct portable-update guidance and developer verification links, and set the next development prefix to1.0.3. Application behavior remains the reviewed and fully accepted PR37 source. Validation: five actual Markdown files pass canonical lint; actionlint and signed-commit hooks pass. Exact-head full hosted checks are running. Production publication and downloaded-artifact signature/provenance verification remain required. MSI remains next release per the owner's latest decision. OpenSSF remains70%, not passing. The owner expressly authorized completion without further human-review requests. This is a release-specific waiver, not a fabricated personal-read acknowledgement. Preserve all technical/security/signature gates. Substantial AI assistance: Codex GPT-6. Refs #33, #34 and KofTwentyTwo/standards#45. --------- Signed-off-by: James Maes <james@kof22.com> Co-authored-by: Codex GPT-6 <noreply@openai.com>
2.7 KiB
Security Policy
Reporting a vulnerability
Do not open a public issue for a security problem.
Report it privately through GitHub's private vulnerability reporting (the repository's Security tab, then Report a vulnerability). That is the only reporting channel.
Security contact: James Maes, maintainer (reached through the private reporting link above).
Please include the affected version, how to reproduce it, and the impact you see. The app's attack surface is described in its threat model.
What to expect
KofTwentyTwo follows coordinated vulnerability disclosure. Timeframes are counted from the day the report arrives and come from the KofTwentyTwo security program (targets until the standards reach v1.0.0, commitments from then on):
| Step | Target |
|---|---|
| Acknowledge the report | 7 days |
| Assess it: confirm or reject, with a severity | 14 days |
| Release a fix for a CRITICAL vulnerability | 7 days |
| Release a fix for a HIGH vulnerability | 30 days |
| Release a fix for a MEDIUM vulnerability | 90 days |
| Release a fix for a LOW vulnerability | The next release |
| Publish the advisory (GitHub Security Advisory, CVE where applicable) | When the fix ships, or 90 days after the report, whichever comes first |
Reporters are credited in the advisory unless they ask not to be.
Supported versions
| Version | Security fixes |
|---|---|
| Latest minor release | Yes |
| Older | No; update in place with Help → Check for updates, or install the latest release |
Only the latest minor release receives fixes; a line stops receiving security fixes when the next minor version is released. After a new major version, the previous major's last minor receives security fixes for 6 months.
Code signing
Public Windows releases require Authenticode signing of the final shipped binaries and installers. Publication fails closed until the approved Azure signing identity and expected publisher, trust and timestamp are verified. Unsigned test fixtures are not releases.
Verify final signatures, SHA256SUMS and provenance attestations as described in the
Developer Guide and
release signing instructions. No historical exception
is claimed as permission to publish unsigned application releases.
Published vulnerabilities
Fixed vulnerabilities are published as GitHub Security Advisories.