scottk/secureblue
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/secureblue.git synced 2025-11-15 17:44:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: formatting cleanup

Browse Source
This commit is contained in:
qoijjj
2024-10-05 22:43:15 -07:00
committed by GitHub
parent 6a63952f07
commit 7867bb22a1
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -19,11 +19,11 @@ secureblue applies hardening with the following goals in mind:
- 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 by default where they exist, so long as this has no security implications (for example, disabling vscode data collection by default on `dx` images) - Disabling metrics and data collection by default where they exist, so long as this has no security implications
The following are not in scope: The following are not in scope:
- 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 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 hardened-chromium with Brave or ungoogled-chromium. Both of them make changes that sacrifice security for "privacy", such as enabling MV2. <sup>[why?](https://developer.chrome.com/docs/extensions/develop/migrate/improve-security)</sup> - Anything related to "degoogling" chromium. For example, we will not be replacing [hardened-chromium](https://github.com/secureblue/hardened-chromium) with Brave or ungoogled-chromium. Both of them make changes that sacrifice security for "privacy", such as enabling MV2. <sup>[why?](https://developer.chrome.com/docs/extensions/develop/migrate/improve-security)</sup>
# Hardening # Hardening