mirror of
https://github.com/trimstray/the-practical-linux-hardening-guide.git
synced 2025-12-06 09:12:46 +01:00
@@ -1,6 +1,6 @@
|
||||
# Contributing
|
||||
|
||||
If you would like to support this project, have an interesting idea how to improve the operation of this tool, or if you found some errors-- fork this, add your fixes, and add a pull request of your branch to the **master branch**.
|
||||
If you would like to support this project, have an interesting idea how to improve the operation of this tool, or if you found some errors - fork this, add your fixes, and add a pull request of your branch to the **master branch**.
|
||||
|
||||
## Signature of commit
|
||||
|
||||
|
||||
@@ -113,7 +113,7 @@ On the other hand, these standards are complicated checklists (often for newbies
|
||||
Hardening is not a simple process. You must devote a lot of time. Here are general rules following common best practices:
|
||||
|
||||
- Never use root account for anything that does not require it
|
||||
- Only ```sudo``` individual commands
|
||||
- Only `sudo` individual commands
|
||||
- Never set a server to run as root (except for initialization time) and ensure that it exits all unnecessary privileges before accepting requests
|
||||
- Ssecure your firewall the best you can and forbid all unnecessary access
|
||||
- Do not install unnecessary or unstable software
|
||||
|
||||
Reference in New Issue
Block a user