fail2rest is a small REST server that aims to allow full administration of a fail2ban server via HTTP
fail2rest will eventually be used as a backend to a small web app to make fail2ban administration and reporting easier.
fail2rest is written in Golang, so it requires a working Golang installation. If you have never used Golang before install it from your package manager, and then follow these instructions to setup your enviroment.
Some libraries currently are not building on older versions of Go, I recommend running the newest stable of Golang.
Once you have a working Golang installation all you need to do is run
go get -v github.com/sean-der/fail2rest
go install -v github.com/sean-der/fail2rest
fail2rest will now be available as a binary in your GOPATH, you can run 'fail2rest' from the command line, or copy it somewhere else to make it available to all users.
Use whereis fail2rest to locate your fail2rest binary.
Next you need to configure fail2rest, and then finally make it a system service.
fail2rest is configured via config.json, the default is located here.
To load your config.json you use the --config flag fail2rest --config=my_config.json
fail2rest has two options that be configured via config.json
- Fail2banSocket - The path to the fail2ban socket, can usually be found via
grep socket /etc/fail2ban/fail2ban.confyou also have to run fail2rest as a user who has permissions to use this socket - Addr - The address that fail2rest is served upon, it is usually best so serve to the loopback, and then allow access via nginx see an example config in the fail2web repository
The default configuration file used by init-scripts is /etc/fail2rest.json. You should download the config to your /tmp/ dir and modify it to your needs.
cd /tmp/
wget https://raw.githubusercontent.com/sean-der/fail2rest/master/config.json
Once you finished editing the configuration file, you should move it from /tmp/config.json to /etc/fail2rest.json executing mv /tmp/config.json /etc/fail2rest.json
Once you have a config.json all you need to do is run fail2rest --config config.json
However, fail2rest is designed to run as a service, so init scripts are provided that allow easy management of fail2rest. They can be found here Download the appropriate init file your Distribution. You may need to customize your init script to load your config.json, but most scripts default to /etc/fail2rest.json
To run as a service you can either copy or create symlinks for systemd and the fail2rest binary. The systemd file shold be added to /etc/systemd/system/fail2rest.service and the the binary to /usr/bin/fail2rest. This scenario will use the symlinks in order to always use the latest files. You should run the commands with sudo if not logged in as root:
ln -s $GOPATH/bin/fail2rest /usr/bin/
Debian
ln -s $GOPATH/src/github.com/sean-der/fail2rest/init-scripts/systemd /etc/systemd/system/fail2rest.service
Other Linux
ln -s $GOPATH/src/github.com/sean-der/fail2rest/init-scripts/systemd /usr/lib/systemd/system/fail2rest.service
Enable fail2rest service to run at startup
systemctl enable fail2rest.service
Run the following systemd command to start the fail2rest service
systemctl start fail2rest.service
Verify that the fail2rest service it is active and running
systemctl status fail2rest.service
The MIT License (MIT)
Copyright (c) 2014 Sean DuBois
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.