docs: add SECURITY.md with private vulnerability reporting process#445
Merged
Conversation
Documents how to privately report security issues via GitHub's Private Vulnerability Reporting (preferred) or Discord (fallback). Covers acknowledgement SLA, supported versions, scope (VM escape, jailer bypass, guest-to-host escalation), and safe-harbor language for good-faith research. Cross-links from README "Getting Help" and CONTRIBUTING "Reporting Issues". Addresses #440.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SECURITY.mddocumenting how to privately report vulnerabilities (GitHub Private Vulnerability Reporting as primary channel, Discord DM as fallback).0.8.x), scope (VM escape, jailer bypass, guest-to-host escalation, image handling, host-side memory safety), and safe-harbor language for good-faith research.README.md"Getting Help" andCONTRIBUTING.md"Reporting Issues" so researchers can find the policy.Addresses #440 item 1 (SECURITY.md).
Remaining follow-ups for the maintainers (not code)
SECURITY.mdalready points at/security/advisories/new, but that form only works once the setting is enabled.Test plan
SECURITY.mdrenders on GitHub (standard Markdown, checked table/list syntax).SECURITY.mdresolve:/security/advisories/new, Discord invite, no dangling references.README.mdandCONTRIBUTING.mdpointers render as expected.0.8.x-only support window.