filemaker-fail2ban
Fail2ban rules for FileMaker Server
These files files can be added to a fail2ban installment so that the relevant FileMaker Server logs will be included.
To install the fail2ban core files, you can use the source at fail2ban.org, or a Mac OS package manager like MacPorts or Homebrew.
Installation
For MacPorts, the install looks like this:
sudo port install fail2ban
To install from source, the process is along these lines:
- open the Terminal
- fetch source (currently 0.9.3):
curl -O https://codeload.github.com/fail2ban/fail2ban/zip/master - unzip the archive:
tar xf master cd fail2ban-master- run the installer script:
sudo python setup.py install - create the run directory (may already be present):
sudo mkdir /var/run/fail2ban/ - create the file at /Library/LaunchDaemons/org.fail2ban.plist with content from below:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Disabled</key>
<false/>
<key>Label</key>
<string>fail2ban</string>
<key>ProgramArguments</key>
<array>
<string>/usr/local/bin/fail2ban-client</string>
<string>start</string>
</array>
<key>RunAtLoad</key>
<true/>
</dict>
</plist>
- load the launchctl .plist:
sudo launchctl load -w /Library/LaunchDaemons/org.fail2ban.plist
Configuration
Since fail2ban version 0.9x, paths can no longer containg spaces.
To work around this, run the following command:
sudo ln -s "/Library/FileMaker Server/" /Library/FileMakerServer
Next, to enable the FileMaker filter, you'll need to add something like the following into your jail.local file (which you may need to create):
[filemaker-client]
enabled = true
action = pf[name=filemake-client, port=5003,16001,http,https]
dest = [email protected]
filter = filemaker-client
logpath = /Library/FileMakerServer/Logs/Event.log
maxretry = 6
If using the Ubuntu style macros this could be written more simply as:
[filemaker-client]
enabled = true
port = 5003,16001,http,https
filter = filemaker-client
logpath = /Library/FileMakerServer/Logs/Event.log
maxretry = 6
Make sure the following values are defined in the [DEFAULT] section of the jail.conf file or at beginning of jail.local:
# email to receive start, stop, ban, and unban notifications
destemail = [email protected]
# This is servername, not servername.domain.com
hostname = `hostname -s`
banaction = pf
The following must be added to the end of the /etc/pf.conf file to enable the fail2ban's ability to block addresses:
table <fail2ban> persist
block drop log quick from <fail2ban> to any
Reload the settings for PF:
sudo pfctl -f /etc/pf.conf
If not already enabled (likely), you'll need to enable PF to start filtering connections:
sudo pfctl -e
Create a script at /etc/periodic/800.fail2ban-rotate-log to rotate log file in case it starts getting big:
#!/bin/sh
# 2017-04-06 simon_b: created file
logPath="/var/log/fail2ban.log"
macPortsFail2ban="/opt/local/bin/fail2ban-client"
apache_version=$(/usr/sbin/httpd -version | head -1 | cut -d "/" -f 2 | cut -d "." -f 1,2)
if [ "$apache_version" == "2.2" ]; then
# Older systems can use newsyslog, but this will rotate log file regardless of size.
/usr/sbin/newsyslog -F "$logPath"
else
# Rotate out the log if bigger than 40 MB, keeping current log at same file name. Requires Apache 2.4+ (Yosemite or better).
/usr/sbin/rotatelogs -L "$logPath" 40M
fi
if [ -s ${macPortsFail2ban} ]; then
# Using MacPorts:
"$macPortsFail2ban" set logtarget "$logPath" >/dev/null
else
# Make fail2ban start using the new log file.
/usr/local/bin/fail2ban-client set logtarget "$logPath" >/dev/null
fi
Use sudo chmod ug+x /etc/periodic/800.fail2ban-rotate-log to make the script executable.
Yosemite+ Configuration
If using 10.10 or better, we can make an additional improvement. This however requires making a change to how FileMaker Server writes out the web server logs. Follow the directions at https://blog.beezwax.net/2015/06/30/keep-filemaker-server-web-logs-at-fixed-paths/ for details.
Once done, add the following to your jail.local file:
# Giving multiple log files in logpath would generate errors. Because there is
# a space in the path? So instead, we are creating separate entries for each log file.
[apache-badbots-1]
enabled = true
filter = apache-badbots
logpath = /Library/FileMakerServer/HTTPServer/logs/access_log
action = pf[name=apache-badbots, port="http,https"]
sendmail-whois[name=%(hostname)s, dest=%(destemail)s, sender=%(hostname)s]
maxretry = 2
[apache-badbots-2]
enabled = true
filter = apache-badbots
logpath = /Library/FileMakerServer/HTTPServer/logs/ssl_access_log
action = pf[name=apache-badbots, port="http,https"]
sendmail-whois[name=%(hostname)s, dest=%(destemail)s, sender=%(hostname)s]
maxretry = 2
[apache-badbots-3]
enabled = true
filter = apache-badbots
logpath = /Library/FileMakerServer/HTTPServer/logs/fmsadminserver_access_log
action = pf[name=apache-badbots, port="http,https"]
sendmail-whois[name=%(hostname)s, dest=%(destemail)s, sender=%(hostname)s]
maxretry = 2
[apache-auth-1]
enabled = true
filter = apache-auth
logpath = /Library/FileMakerServer/HTTPServer/logs/error_log
action = pf[name=apache-auth, port="http,https"]
sendmail-whois[name=%(hostname)s, dest=%(destemail)s, sender=%(hostname)s]
maxretry = 4
[apache-auth-2]
enabled = true
filter = apache-auth
logpath = /Library/FileMakerServer/HTTPServer/logs/ssl_error_log
action = pf[name=apache-auth, port="http,https"]
sendmail-whois[name=%(hostname)s, dest=%(destemail)s, sender=%(hostname)s]
maxretry = 4
[apache-noscript-1]
enabled = true
action = pf[name=apache-noscript, port="http,https,16000"]
sendmail-whois[name=%(hostname)s, dest=%(destemail)s, sender=%(hostname)s]
filter = apache-noscript
logpath = /Library/FileMakerServer/HTTPServer/logs/error_log
[apache-noscript-2]
enabled = true
action = pf[name=apache-noscript, port="http,https,16000"]
sendmail-whois[name=%(hostname)s, dest=%(destemail)s, sender=%(hostname)s]
filter = apache-noscript
logpath = /Library/FileMakerServer/HTTPServer/logs/ssl_error_log
fail2ban logs
Fail2ban keeps a log file at /var/log/fail2ban. This will list the jail name (the part in brackets in configuration file) and the IP address that triggered the entry.
Here's an example (with IP addresses obfuscated):
$ tail /var/log/fail2ban.log
2016-05-17 10:29:29,420 fail2ban.filter [21867]: INFO [postfix] Found 176.218.x.x
2016-05-17 10:30:00,468 fail2ban.filter [21867]: INFO Log rotation detected for /var/log/mail.log
2016-05-17 10:32:35,989 fail2ban.filter [21867]: INFO [postfix] Found 77.247.x.x
2016-05-17 10:36:52,351 fail2ban.filter [21867]: INFO [postfix] Found 167.0.x.x
2016-05-17 10:38:20,473 fail2ban.filter [21867]: INFO [postfix] Found 91.92.x.x
2016-05-17 10:38:20,474 fail2ban.filter [21867]: INFO [postfix] Found 91.92.x.x
2016-05-17 10:38:42,528 fail2ban.filter [21867]: INFO [postfix] Found 91.92.x.x
2016-05-17 10:38:42,529 fail2ban.filter [21867]: INFO [postfix] Found 91.92.x.x
2016-05-17 10:38:42,883 fail2ban.actions [21867]: NOTICE [postfix] Ban 91.92.x.x
2016-05-17 10:38:43,533 fail2ban.filter [21867]: INFO [postfix] Found 74.63.x.x
Listing IPs that are currently blocked
sudo pfctl -t fail2ban -T show
This should give some output similar to this (IP addresses obfuscated):
No ALTQ support in kernel
ALTQ related functions disabled
176.218.x.x/32
167.0.x.x/32
91.92.x.x/32
Reference
For fail2ban documentation, see http://www.fail2ban.org.
Our original blog post is at http://blog.beezwax.net/2013/05/06/fail2ban-with-filemaker-server/ and provides some background on the initial implementation. One recent change that dates the blog however is that ipfw is no longer available as of Mac OS 10.10 (Yosemite), so you must use pf as your action/banaction.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent