Skip to content

Commit ba799d5

Browse files
authored
Add SECURITY.md with threat model for PyManager. (#314)
Fixes #304
1 parent aebc2b5 commit ba799d5

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

.github/SECURITY.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Security Policy
2+
3+
## Reporting a Vulnerability
4+
5+
Please use [GitHub Security Advisories](https://github.com/python/pymanager/security/advisories) to report potential issues to this project.
6+
7+
Alternatively, follow [the main security page](https://www.python.org/dev/security/) for alternate ways to report,
8+
bearing in mind that eventually we will create a report using GHSA if needed.
9+
10+
## Threat Model
11+
12+
Our threat model for the Python install manager makes the following assumptions:
13+
14+
* users are using the default index from python.org
15+
* TLS/HTTPS connections are secure and are not intercepted or tampered with
16+
* users are using the default configured directory structure
17+
* users are running with a reasonable privilege level for their environment
18+
* all reconfigured settings are intentional, including environment variables
19+
* all configuration from outside of the install manager is intentional
20+
* our code-signing infrastructure is not compromised
21+
22+
Any reported vulnerability that requires any of these assumptions to be broken will be closed and treated as a regular bug or a non-issue.
23+
24+
Notably, an index is considered to include a trustworthy set of install instructions,
25+
and so can arbitrarily modify a user's machine by design.
26+
Once a user is installing from a non-default feed,
27+
whether through modified configuration (file or environment variable) or intercepted network traffic,
28+
we cannot treat issues arising from the contents of that feed as security critical.

0 commit comments

Comments
 (0)