[Bug 1696591] Re: fail2ban default configuration should be "backend = systemd" in Xenial

2022-05-30 Thread Tobias Brox
This is a problem for focal as well

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696591

Title:
  fail2ban default configuration should be "backend = systemd" in Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1696591/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696591] Re: fail2ban default configuration should be "backend = systemd" in Xenial

2018-01-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: fail2ban (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696591

Title:
  fail2ban default configuration should be "backend = systemd" in Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1696591/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1696591] Re: fail2ban default configuration should be "backend = systemd" in Xenial

2017-06-07 Thread Andrew
** Description changed:

- The default install of fail2ban in Xenial has "/etc/fail2ban/jail.conf" 
option "backend=auto", which watches "/var/log/auth.log", which in 16.04 is an 
empty file on the default configuration of sshd (it logs verbosely to 
journalctl).
+ The default install of fail2ban has "/etc/fail2ban/jail.conf" option 
"backend=auto", which watches "/var/log/auth.log", which in 16.04 is an empty 
file on the default configuration of sshd (it logs verbosely to journalctl).
  My opinion is that fail2ban ought to have a working default configuration for 
the default jail.
+ 
+ Obviously Ubuntu is following Debian on this, relevant Debian bug:
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770171

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696591

Title:
  fail2ban default configuration should be "backend = systemd" in Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1696591/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1696591] Re: fail2ban default configuration should be "backend = systemd" in Xenial

2017-06-07 Thread Andrew
** Summary changed:

- fail2ban default configuration should be "backend = systemd"
+ fail2ban default configuration should be "backend = systemd" in Xenial

** Description changed:

- The default install of fail2ban has "/etc/fail2ban/jail.conf" option 
"backend=auto", which watches "/var/log/auth.log", which in 16.04 is an empty 
file on the default configuration of sshd (it logs verbosely to journalctl).
+ The default install of fail2ban in Xenial has "/etc/fail2ban/jail.conf" 
option "backend=auto", which watches "/var/log/auth.log", which in 16.04 is an 
empty file on the default configuration of sshd (it logs verbosely to 
journalctl).
  My opinion is that fail2ban ought to have a working default configuration for 
the default jail.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696591

Title:
  fail2ban default configuration should be "backend = systemd" in Xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/1696591/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs