CSEC_PUBLIC/How-To-Secure-A-Linux-Server
1
0
Fork 0
mirror of https://github.com/imthenachoman/How-To-Secure-A-Linux-Server.git synced 2025-12-06 09:12:47 +01:00
Code Issues Packages Projects Releases Wiki Activity

enhance: fix tips

Browse Source
This commit is contained in:
Laurence
2024-10-15 22:09:41 +01:00
parent 0b1f1cbf6b
commit 928eb2de88
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -2139,8 +2139,8 @@ CrowdSec monitors the logs of your applications (like SSH and Apache) to detect
curl -s https://install.crowdsec.net | sudo sh
```
> [!TIP]
> if `curl | sh` is not your thing, you can find additional install methods [here](https://docs.crowdsec.net/u/getting_started/installation/linux).
> [!TIP]
> if `curl | sh` is not your thing, you can find additional install methods [here](https://docs.crowdsec.net/u/getting_started/installation/linux).
Install the CrowdSec Security Engine:
``` bash
@@ -2157,8 +2157,8 @@ By default whilst CrowdSec is installing the Security Engine it will auto-discov
sudo apt install crowdsec-firewall-bouncer-iptables
```
> ![!TIP]
> If your installation of UFW is not using `iptables` as the backend, you can alternatively install `crowdsec-firewall-bouncer-nftables`. There is no difference in the installed binaries, only the configuration file is different.
> ![!TIP]
> If your installation of UFW is not using `iptables` as the backend, you can alternatively install `crowdsec-firewall-bouncer-nftables`. There is no difference in the installed binaries, only the configuration file is different.
By default whilst the Remediation Component is installing it will auto-configure the necessary settings to work with the Security Engine if deployed on the same host (and if the security engine is not within a container environment).