On Fri, Oct 06, 2006 at 04:20:03PM -0700, Debian Bug Tracking System wrote:
> Source: uae
> Source-Version: 0.8.25-2
>
> We believe that the bug you reported is fixed in the latest version of
> uae, which is due to be installed in the Debian FTP archive:
>
> uae_0.8.25-2.diff.gz
> to pool/contr
On Wed, Jan 04, 2006 at 03:01:35AM +0100, Jeroen van Wolffelaar wrote:
> Fwiw, the Release.gpg file contains two signatures now, both one with the
> 2005 key and the 2006 key, to have a short transition period. The archive
> still validates with the 2005 key, which isn't expired yet, and I think AP
On Mon, Oct 03, 2005 at 10:24:09PM -0400, Yaroslav Halchenko wrote:
> Besides that regular users or sysadmins are not even supposed to "tune"
> failregex to have basic functionality to be performed. Me (and the upstream)
> author are going to incorporate or at least include in the package more
> of
On Sat, Oct 01, 2005 at 03:04:20AM -0400, Yaroslav Halchenko wrote:
> Hi Joshua,
>
> Thank you for you feedback. If you have a moment
> could you please give a try to the "fixed" revision. I've placed in
> changelog entry which states that it is necessary to update config file
> to have the breach
> Thank you for raising the issue. Indeed that is a grave problem.
> Unfortunately upstream author is away for a week or two, thus I will try
> to resolve the issue on my own. I think that I will simply incorporate
> regex for IPs inside failregex config options, thus IP addresses will
> not be ha
Package: fail2ban
Version: 0.5.2-4
Severity: grave
fail2ban's approach to identifying an IP address in a login failure line
is to scan the line for all IP addresses.
Since it is possible to generate false logins from accounts such as
10.2.28.2, it is possible to force fail2ban to block access to
6 matches
Mail list logo
