The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: fail2ban (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu releases hardly get any support even when they're new. Now that a
newer LTS is available, there's no hope.
Support until 2017... yeah, right. Fuck this, once again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just stumbled across this bug trying to diagnose a non-functioning
fail2ban. #15 indicates that a fix is released, but my Precise server
still has 0.8.6-3. Adding the -proposed repository didn't provide a
newer version, although I see that 0.8.7.1-1 is in Quanal. Will this be
made available for
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fail2ban (Ubuntu Precise)
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/954453
This bug was fixed in the package fail2ban - 0.8.7.1-1
---
fail2ban (0.8.7.1-1) experimental; urgency=low
* Minor upstream bugfix release
-- Yaroslav Halchenko deb...@onerussian.com Tue, 31 Jul 2012
21:46:19 -0400
fail2ban (0.8.7-1) experimental; urgency=low
* New upstream
This isn't actually a security bug as it doesn't directly allow an
attacker privileged access to a computer system.
See https://wiki.ubuntu.com/SecurityTeam
** This bug is no longer flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
A fixed version of gamin is in precise-proposed (see bug #926862)
** This bug has been flagged as a security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954453
Title:
fail2ban in
I tried the new gamin-0.1.10-4ubuntu0.1 in precise-proposed and fail2ban
freezes during startup for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954453
Title:
fail2ban in precise defaults to
I killed /usr/lib/gamin/gam_server and now fail2ban is starting OK with
gamin-0.1.10-4ubuntu0.1. We'll see if fail2ban detects log file changes
like it should.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I honestly did not expect that upgrading from an LTS release to a newer
LTS means that some services that was working before, will not work
after.
This should be fixed asap!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Tue, 22 May 2012, Mark Schroeder wrote:
I'm not sure what you want tested.
I know that polling is guaranteed to work ;) sorry if I wasn't clear
-- I wondered if you could test current development version which
is in git which should use inotify by default (to replace gamin)... but
I guess
I'm a developer and at least aware that there is additional
complexity to wrap a standard tar source into an Ubuntu .deb.
I see these:
http://packages.ubuntu.com/precise/fail2ban (standard, ubuntu wrapped)
https://github.com/fail2ban/fail2ban (development)
But I'm not sure of the precise (no
On Thu, 07 Jun 2012, Mark Schroeder wrote:
I'm a developer and at least aware that there is additional
complexity to wrap a standard tar source into an Ubuntu .deb.
I see these:
http://packages.ubuntu.com/precise/fail2ban (standard, ubuntu wrapped)
https://github.com/fail2ban/fail2ban
inotify backend had already merged into upstream's master branch post
0.8.6 release but there were no upstream release yet.
There is an issue reported against functionality of this backend:
https://github.com/fail2ban/fail2ban/issues/44
and it would be great if you could give it some testing. I
I'm not sure what you want tested.
I briefly tried gamin with ssh, and it worked, at least for a bit.
Another friend tried it and reports that his postfix rules
did not result in a ban as expected, though.
I then put it back to 'polling', and that failed to be effective
until I rebooted and
This is caused by gamin bug #926862. A correct fix to gamin is available
and should be applied to that package in preference to changing fail2ban
to use filesystem polling.
As far as I can tell, this is a security issue since fail2ban (and
presumably other monitoring daemons) will silently ignore
Some background:
RedHat ported fail2ban to use pyinotify instead of gamin which seems the
way forward (https://bugzilla.redhat.com/show_bug.cgi?id=658849 and
https://bugzilla.redhat.com/show_bug.cgi?id=551895).
Switching to pyinotify is apparently on the fail2ban roadmap for 0.9.0
at
My observation is a bit different but conclusion is the same: backend =
gamin should be changed to backend = polling.
Fail2ban on two of my machines (one local, one EC2) work with initial
bootup of the system. But once the service is restarted, it stops
receiving events. Changing backend =
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/954453
Title:
Exact same experience here - with backend = polling, as included in
fail2ban 0.8.6-3's /etc/fail2ban/jail.conf, fail2ban uses Gamin and does
not properly monitor /var/log/auth.log and ban as expected. When I
switch this to backend = polling fail2ban works as expected.
--
You received this bug
20 matches
Mail list logo
