This bug was fixed in the package sshguard - 2.3.1-1ubuntu1.1
---
sshguard (2.3.1-1ubuntu1.1) focal; urgency=medium
* Fix path to iptables binaries in the .service unit. LP: #1884848
-- Dimitri John Ledkov Wed, 24 Jun 2020 11:53:44
+0100
** Changed in: sshguard (Ubuntu Focal)
I can confirm that the bug is fixed.
sshguard/now 2.3.1-1ubuntu1.1 amd64
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Hello Malcolm, or anyone else affected,
Accepted sshguard into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/sshguard/2.3.1-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package sshguard - 2.3.1-1ubuntu2
---
sshguard (2.3.1-1ubuntu2) groovy; urgency=medium
* Fix path to iptables binaries in the .service unit. LP: #1884848
-- Dimitri John Ledkov Wed, 24 Jun 2020 11:53:44
+0100
** Changed in: sshguard (Ubuntu)
** Description changed:
+ [Impact]
+
+ * sshguard.service does not start correctly on systems upgraded from bionic
to focal.
+ * sshguard.service hardcodes paths to iptables binary. However, said path
has changed in focal+ in the iptables package.
+ * This issue impacts installations of
Well, this is not a usr-merge bug per-se, but just a bug that usr-merge
actually fixes for people.
iptables in focal has moved from /sbin/iptables to /usr/sbin/iptables.
The hardcoded path in sshguard.service was not updated, and thus is
broken. usr-merged systems do not experience this issue,
@malcscott
At the moment we support split-usr & merged-usr.
Newly installed machines should all be merged-usr, with symlinks making
any paths work.
The dpkg .deb itself, is built as split-usr and existing installations
upgrade and keep split-usr (will be fixed for upgrades to 22.04).
So the
** Changed in: sshguard (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1884848
Title:
sshguard.service uses wrong path for iptables; nothing
None of the machines I've upgraded to focal from bionic have a symlink
in /sbin/iptables.
$ namei -l /sbin/iptables
f: /sbin/iptables
drwxr-xr-x root root /
drwxr-xr-x root root sbin
iptables - No such file or directory
However you're right that a fresh install does have
There should be several symlinks to make this work:
$ namei -l /sbin/iptables
f: /sbin/iptables
drwxr-xr-x root root /
lrwxrwxrwx root root sbin -> usr/sbin
drwxr-xr-x root root usr
drwxr-xr-x root root sbin
lrwxrwxrwx root root iptables -> /etc/alternatives/iptables
drwxr-xr-x root root /
10 matches
Mail list logo
