docs: clarify scope (#319)

This commit is contained in:
qoijjj
2024-07-14 23:27:18 -07:00
committed by GitHub
parent a3701c7e4f
commit c35691a091

View File

@@ -15,10 +15,11 @@ This repo uses [BlueBuild](https://blue-build.org/) to generate hardened operati
- Increase defenses against the exploitation of both known and unknown vulnerabilities. - Increase defenses against the exploitation of both known and unknown vulnerabilities.
- Avoid sacrificing usability for most use cases where possible - Avoid sacrificing usability for most use cases where possible
- Disabling metrics and data collection where they exist, so long as this has no security implications (for example, making vscode data collection opt-in instead of opt-out on `dx` images)
The following are not in scope for this project: The following are not in scope:
- Anything related to "privacy", since Fedora is already sufficiently private and "privacy" often serves as a euphemism for security theater. This is especially true when at odds with improving security. - Anything that sacrifices security for "privacy". Fedora is already sufficiently private and "privacy" often serves as a euphemism for security theater. This is especially true when at odds with improving security.
- Anything related to "degoogling" chromium. For example, we will not be replacing chromium with Brave or ungoogled-chromium. - Anything related to "degoogling" chromium. For example, we will not be replacing chromium with Brave or ungoogled-chromium. Both of them make changes that sacrifice security for "privacy", such as enabling MV2.
## What ## What