Skip to content

Commit 856b971

Browse files
StanFromIrelandJacobCoffeehugovk
authored
Clarify the role PSRT has in handling vulnerability reports for unsupported platforms (GH-1822)
Co-authored-by: Jacob Coffee <jacob@z7x.org> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
1 parent 3d4cf26 commit 856b971

1 file changed

Lines changed: 7 additions & 6 deletions

File tree

security/policy.rst

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -77,12 +77,13 @@ are not treated as vulnerabilities in Python.
7777

7878
As per the :pep:`Unsupported Platforms section of PEP 11 <11#unsupported-platforms>`,
7979
porting Python to an unsupported platform is treated as a third-party project.
80-
If you choose to report such a vulnerability to Python, please follow the
81-
requirements of this guide. Note that these reports may be shared with
82-
parties who expressed interested in the relevant platforms and will
83-
generally be handled according to the relevant maintainers' security
84-
policies. These reports may closed if the maintainers are unknown or
85-
unresponsive.
80+
For these reports, the PSRT treats them as vulnerability reports for a third-party
81+
port, not as Python vulnerabilities.
82+
If you choose to report such an issue to Python, follow the requirements
83+
of this guide and include the relevant platform and maintainer context.
84+
The PSRT forwards these reports to platform maintainers (or other interested
85+
parties) and they are usually handled under the relevant maintainers' security
86+
policies. These reports will be closed if the maintainers are unknown or unresponsive.
8687

8788
What to include and how to structure a vulnerability report?
8889
------------------------------------------------------------

0 commit comments

Comments
 (0)