It seems that SSHguard 1.7 dropped support for the "
hosts.allow" file. Since I already wrote about how to setup SSHguard 1.6.x on FreeBSD using TCP Wrappers, I thought I should offer a quick update for SSHguard 1.7.x.
Please note that the process shown here assumes FreeBSD 10.x and SSHguard 1.7.x. The directions will go through five major steps: (1) Install SSHguard, (2) get SSHguard configured, (3) get IPFW started, (4) restart to bring it all together and make sure it works. Lastly, I'll cover (5) how to look at what is happening.
First, install SSHguard from the ports collection or upgrade it with portmaster, as needed. For example, to install it for the first time, you could:
su cd /usr/ports/security/sshguard make install
When prompted, select IPFW. To clean up unnecessary files, you can type "
make clean", but this step is optional. If you already have it installed, check the FreeBSD Handbook for directions on using portsnap (section 4.5) and portmaster (section 22.214.171.124) to upgrade the port. Just be careful to avoid breaking any other ports in the process.
Once you have SSHguard 1.7.x installed, you'll need to configure it. Start by whitelisting any necessary IP addresses by adding them to the file "
/usr/local/etc/sshguard.whitelist". Only add one IP address per line. I recommend preceding those lines with a comment to help you remember why you added them. Comments are lines that begin with a ”
#”. So you might have something like this:
# Don't block the VPN server. 126.96.36.199
The last step in configuring SSHguard is to tell your system to run it at boot time. Do this by adding these lines to "
# Start SSHGuard sshguard_enable="YES"
Now we should be ready to move on to the IPFW system. This replaces the much easier to manage TCP Wrappers system we used in SSHguard 1.6, a.k.a. the "
/etc/hosts.allow" file. The first step is to enable the IPFW firewall at boot time by adding these lines to
firewall_enable="YES" firewall_logging="YES" firewall_type="open"
If you don't want to reboot the system, you can manually start the firewall by running "
service ipfw start" as root. This is a great way to make sure that all your settings are right so far. However, don't do this unless you have physical access to the server. Changing firewall settings when you only have a network connection to the system is a quick way to get locked out of it by accident. The steps I've listed here won't do that, but I don't know what other changes you've made before reading this article, so I'm including this warning just in case.
Now that we have IPFW running, SSHguard will report suspicious activity to what IPFW calls "table 22." We need to tell IPFW to block everything listed in table 22. To do this, edit
/etc/rc.local and add the following lines. If the file already exists, skip the first line and add the rest to the end of the file.
#!/bin/sh echo Adding sshguard to IPFW settings /sbin/ipfw -q add 55000 deny all from 'table(22)' to any
Next, allow the
/etc/rc.local script to run during system startup. To do that, run this command as root:
chmod 0755 /etc/rc.local
Restart the system with "
shutdown -r now" to confirm that this script runs properly at startup. Watch for it when the startup messages scroll by on console and also check the settings by logging in as root and typing "
That is basically it. I encourage you to review these steps and try to learn what they do and why they work that way. You'll probably find ways to adjust this process to fit your system a little better. However, this should get you started.
If you ever want to know what the IPFW firewall is doing, you can check its rules by running "
ipfw list" as root.
If you want to see the SSHguard rules, specifically, you need to look at table 22. SSHguard keeps these rules isolated in their own table, so they don't accidentally overwrite anything else nor create any other unpredictable outcomes. To look at table 22, just run "
ipfw table 22 list" as root.
Lastly, if you're setting up SSHguard for the first time, please read the end of my older article as well. It includes some advice that is still relevant. Also, remember that SSHguard should only a piece of your risk mitigation strategy. No single product or trick will ever cover you completely. Even if you're not an expert in Information Security, you should always strive for defense in depth as a way to reduce your risks.