github
/
fail2ban
mirror of https://github.com/fail2ban/fail2ban
1
0
Fork 0
Code Issues Releases Wiki Activity

d/control: add nftables references 

The nftables framework replaces iptables. The fail2ban software already
includes support for nftables, so reflect that in the packaging.

Also, no need to `Recommends: iptables`, since is installed by default in every
Debian system. Instead, do `Recommends: nftables`.

Signed-off-by: Arturo Borrero Gonzalez <arturo@debian.org>
pull/2221/head
Arturo Borrero Gonzalez 2018-03-09 13:00:03 +01:00 committed by Yaroslav Halchenko
parent 400b260a32
commit b67dc5e908
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
debian/control vendored
View File

@ -17,7 +17,7 @@ Standards-Version: 4.1.3
Package: fail2ban
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}, lsb-base (>=2.0-7)
Recommends: python, iptables, whois, python3-pyinotify, python3-systemd
Recommends: python, nftables, whois, python3-pyinotify, python3-systemd
Suggests: mailx, system-log-daemon, monit, sqlite3
Description: ban hosts that cause multiple authentication errors
Fail2ban monitors log files (e.g. /var/log/auth.log,
@ -34,8 +34,8 @@ Description: ban hosts that cause multiple authentication errors
to be used with a variety of files and firewalls. Following recommends
are listed:
.
- iptables -- default installation uses iptables for banning. You most
probably need it
- iptables/nftables -- default installation uses iptables for banning.
nftables is also suported. You most probably need it
- whois -- used by a number of *mail-whois* actions to send notification
emails with whois information about attacker hosts. Unless you will use
those you don't need whois