bronze/mayfrost-guides
1
0
Fork 0
mirror of https://github.com/mayfrost/guides.git synced 2024-10-31 23:16:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update SECURITY.md

Browse Source
This commit is contained in:
mayfrost 2018-11-25 19:09:10 -03:00 committed by GitHub
parent 62affbd8b8
commit db9e09bee5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
SECURITY.md
View File

@ -78,7 +78,7 @@ Not necessarily meant to be followed step by step, although it is recommended. S
* __Level 48__: Use only libre software (software "free as in freedom"). * __Level 48__: Use only libre software (software "free as in freedom").
* __Level 49__: Reduce the amount of software installed in your computer. * __Level 49__: Reduce the amount of software installed in your computer.
* __Level 50__: Opt for text-based programs with less library dependencies than their GUI counterparts. * __Level 50__: Opt for text-based programs with less library dependencies than their GUI counterparts.
* __Level 51__: Support the GPL license as to prevent proprietary license wrapping (as with BSD/MIT/Apache licenses) by which you would lose critical updates and further features. GPLv3 in specific to prevent tivoization, a hardware level lockout method. * __Level 51__: Support the GPL license as to prevent proprietary license wrapping (as with BSD/MIT/Apache licenses) by which you would lose critical updates and further features. GPLv3 also prevents tivoization, a hardware level lockout method.
* __Level 52__: Deduplicate efforts and converge strategies to achieve a "tight base system" in common (use the koan "if is not strictly necessary it should be strictly optional, but still optional"), and that means making things modular and avoiding unnecessary dependencies instead of trusting "crypto libraries" like in Python. * __Level 52__: Deduplicate efforts and converge strategies to achieve a "tight base system" in common (use the koan "if is not strictly necessary it should be strictly optional, but still optional"), and that means making things modular and avoiding unnecessary dependencies instead of trusting "crypto libraries" like in Python.
## Exit Level Security ## Exit Level Security