ArchLinux:Security: Difference between revisions
m (→Firewall) |
|||
Line 8: | Line 8: | ||
= {{Icon24|sitemap}} Networking = | = {{Icon24|sitemap}} Networking = | ||
== {{Icon|notebook}} Firewall == | == {{Icon|notebook}} Firewall == | ||
Uncomplicated Firewall or [[archwiki:Uncomplicated Firewall|ufw]] is a great choice and it's simple to setup. | Uncomplicated Firewall or [[archwiki:Uncomplicated Firewall|ufw]] is a great choice and it's simple to setup. [//cipherdyne.org/psad/ psad] is a collection of three lightweight system daemons (two main daemons and one helper daemon) that run on Linux machines and analyze iptables log messages to detect port scans and other suspicious traffic. | ||
{{Console|1=pacaur -S ufw}} | |||
Install both packages. | |||
{{Console|1=pacaur -S psad ufw}} | |||
Setup some basic rules that will allow SSH but deny everything else. | Setup some basic rules that will allow SSH but deny everything else. | ||
{{Console|1=sudo ufw default deny|2=sudo ufw allow SSH}} | {{Console|1=sudo ufw default deny|2=sudo ufw allow SSH}} |
Revision as of 00:32, 25 July 2017
UNDER CONSTRUCTION: The document is currently being modified! |
Introduction
This is geared at providing a checklists one can walk through after setting up a new Arch Linux installation that has an open connection to the internet. Whether it is a server or just a machine at home that you have ports open on; some if not all of this information might be useful to you.
WARNING: While I have administered BSD and Linux machines for many years now, I am not a security expert! |
Networking
Firewall
Uncomplicated Firewall or ufw is a great choice and it's simple to setup. psad is a collection of three lightweight system daemons (two main daemons and one helper daemon) that run on Linux machines and analyze iptables log messages to detect port scans and other suspicious traffic.
Install both packages.
# pacaur -S psad ufw |
Setup some basic rules that will allow SSH but deny everything else.
# sudo ufw default deny # sudo ufw allow SSH |
WARNING: It is highly recommended to open a new SSH window at this point (without closing the current) and verify SSH access still works. |
Enable ufw on boot and then start the service.
# sudo systemctl enable ufw # sudo ufw enable |
To query the rules being applied use the status command argument.
# sudo ufw status |
To see a list of all applications in the ufw database use the app argument.
# sudo ufw app list |
If the creation of a custom application is needed, make one in the /etc/ufw/applications.d directory.
# sudo vim /etc/ufw/applications.d/mycustomapp |
[mycustomapp] title=My Custom App description=Custom App for Blah ports=11000:11005/tcp|11010/udp |
This would create a custom application filter on ports 11000-11005 using tcp and port 11010 using udp. It would then merely need to be enabled.
# sudo ufw allow mycustomapp |
Blacklisting IPs
It might be desirable to blacklist an IP address, maybe you have seen brute force attempts from it or maybe you just want to block it. This can be done by editing /etc/ufw/before.rules. Add the blacklisting to the end of the file before COMMIT.
# sudo vim /etc/ufw/before.rules |
## blacklist section # block just 8.8.8.8 -A ufw-before-input -s 8.8.8.8 -j DROP # block 8.8.*.* -A ufw-before-input -s 8.8.0.0/16 -j DROP # don't delete the 'COMMIT' line or these rules won't be processed COMMIT |
Disable Remote Ping
Change ACCEPT to DROP in the following lines of /etc/ufw/before.rules.
# ok icmp codes -A ufw-before-input -p icmp --icmp-type destination-unreachable -j ACCEPT -A ufw-before-input -p icmp --icmp-type source-quench -j ACCEPT -A ufw-before-input -p icmp --icmp-type time-exceeded -j ACCEPT -A ufw-before-input -p icmp --icmp-type parameter-problem -j ACCEPT -A ufw-before-input -p icmp --icmp-type echo-request -j ACCEPT |
If IPv6 is being used the same can be done inside of /etc/ufw/before6.rules as well.