Skip to content

Security Policy: Fix an rST spacing bug #1813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
StanFromIreland merged 3 commits into from
May 30, 2026
Merged

Security Policy: Fix an rST spacing bug #1813

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
397f992
Security Policy: Fix an rST spacing bug
StanFromIreland May 27, 2026
f81612e
Grammar + hunspell
StanFromIreland May 27, 2026
fcee3cc
Bénédikt;s review
StanFromIreland May 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 3 additions & 4 deletions security/policy.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,7 @@ to report a bug as a vulnerability.

Vulnerabilities must be exploitable from code, configurations,
pre-conditions, or deployments that may exist in the real world.
A vulnerability that only affecting code
unlikely to be used in a production program
A vulnerability that only affects code unlikely to be used in a production program
Comment thread
StanFromIreland marked this conversation as resolved.
Outdated
will not be accepted.

Documented functionality is not considered a vulnerability.
Expand Down Expand Up @@ -81,7 +80,7 @@ porting Python to an unsupported platform is treated as a third-party project.
If you choose to report such a vulnerability to Python, please follow the
requirements of this guide. Note that these reports may be shared with
parties who expressed interested in the relevant platforms and will
generally be handled according to the relevant maintainers' security
generally be handled according to the relevant maintainer's security
Comment thread
StanFromIreland marked this conversation as resolved.
Outdated
policies. These reports may closed if the maintainers are unknown or
unresponsive.

Expand Down Expand Up @@ -133,7 +132,7 @@ Here's what to expect for how a vulnerability report will be handled:

* Reporter reports the vulnerability privately to the PSRT.
* If the PSRT determines the report isn't a vulnerability, the reporter
may open a public issue.
may open a public issue.
* If the PSRT determines the report is a vulnerability, the PSRT will
accept the report and a CVE ID will be assigned by the PSF CNA.
* Once a public pull request containing a fix is merged to CPython,
Expand Down
Loading