Re: [SSHGuard-users] Change sshguard backend to hosts for transition from iptables to nftables?

[Kevin Z. <kev...@gm...>]

Hi there,

On 3/14/21 9:08 PM, 8187--- via sshguard-users wrote:
> We're moving a number of Debian machines from iptables to nftables 
> (nft), and it looks as if the sooner we purge iptables and ufw and use 
> only nftables the better.  While this occurs, we would like to try to 
> run sshguard with the "tcpwrapper" hosts backend, and write the blocked 
> hosts to /etc/hosts.deny.  We could install from source and manually set 
> the backend in sshguard.conf, but that would also require changes to the 
> systemd sshguard.services file.

Unless the package doesn't have sshg-fw-hosts (built by default) 
installed in libexec, you shouldn't have to build SSHGuard from source 
to use the hosts (tcpwrapper) backend.

You should just be able to set the BACKEND to sshg-fw-hosts in 
sshguard.conf.

> Unfortunately, Debian 9, after building the dependencies:
> 
> autoconf automake byacc flex gcc python-docutils
> 
> fails ./configure:
> 
> <<
> config.status:1194: error: Something went wrong bootstrapping makefile 
> fragments
>      for automatic dependency tracking.  If GNU make was not used, consider
>      re-running the configure script with MAKE="gmake" (or whatever is
>      necessary).  You can also try re-running configure with the
>      '--disable-dependency-tracking' option to at least be able to build
>      the package (albeit without support for automatic dependency tracking).
>  >>

This could be an automake issue where it thinks some file got touched. 
Which tarball did you extract to get this message?

Regards,
Kevin