Package: fail2ban
Version: 0.10.2-2.1
Followup-For: Bug #888711
Dear Maintainer,
fail2ban 0.10.2-2.1 still ships the incorrect sshd-ddos.conf and
sshd-aggressive.conf files. Neither ddos nor aggressive are defined
parameters so these files should be rewritten as shown in the
attachements, that
On Mon, 29 Jan 2018, peter.ch...@data61.csiro.au wrote:
> ...
> Alternatively, remove sshd-ddos.conf and sshd-aggressive.conf from the
> package
they aren't shipped with 0.10 version of the package -- they are left
from previous versions:
$> wget
> "SZÉPE" == SZÉPE Viktor writes:
SZÉPE> Idézem/Quoting Peter Chubb :
>> Package: fail2ban Version: 0.10.2-1 Severity: normal
>>
>> Dear Maintainer,
>>
>> After upgrading fail2ban, it no longer starts. The error message
>> is:
>>
>> fail2ban
Idézem/Quoting Peter Chubb :
Package: fail2ban
Version: 0.10.2-1
Severity: normal
Dear Maintainer,
After upgrading fail2ban, it no longer starts.
The error message is:
fail2ban Failed during configuration: Bad value substitution:
option 'mode' in section
Package: fail2ban
Version: 0.10.2-1
Severity: normal
Dear Maintainer,
After upgrading fail2ban, it no longer starts.
The error message is:
fail2ban Failed during configuration: Bad value substitution:
option 'mode' in section 'Definition' contains an interpolation
key 'ddos' which is not a
5 matches
Mail list logo