scottk/secureblue
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/secureblue.git synced 2025-10-31 10:27:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: further clarify why mv2 won't be enabled (#395)

Browse Source 
* futher clarify why mv2 won't be enabled

* add link explaining mv3 superior security over mv2

* add space
This commit is contained in:
graphenelover
2024-08-25 22:10:41 +02:00
committed by GitHub
parent 967c7551ad
commit 05392582f4
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -23,7 +23,7 @@ secureblue applies hardening with the following goals in mind:
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. - 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>
# Hardening # Hardening