Your message dated Sat, 14 Feb 2009 10:23:49 -0500
with message-id <[email protected]>
and subject line iptables shouldn't allow recent with --set and --rttl
has caused the Debian Bug report #346034,
regarding iptables shouldn't allow recent with --set and --rttl
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
346034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346034
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iptables
Version: 1.3.4-0.1
Severity: minor
Hi,
I was recently having problems with my recent match to stop SSH
scanners... well, I now found out what was the problem:
I was using the --rttl option in my --set line; this caused all incoming
ssh connections to be rejected; --rttl is only to be used with --rcheck
and --update... :-(
Maybe iptables could catch this mistake?
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.14
Locale: lang=de_de.ut...@euro, lc_ctype=de_de.ut...@euro (charmap=UTF-8)
Versions of packages iptables depends on:
ii libc6 2.3.5-11 GNU C Library: Shared libraries an
iptables recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.4.2-1
Fixed.
--- End Message ---
