netdev - Re: why do we need printk on sending syn flood cookie?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 2 Aug 2010 10:17:16 +0200
From:	Florian Westphal <fw@...len.de>
To:	Franchoze Eric <franchoze@...dex.ru>
Cc:	netdev@...r.kernel.org
Subject: Re: why do we need printk on sending syn flood cookie?

Franchoze Eric <franchoze@...dex.ru> wrote:
>  Just sirious why do we need printk each 1 second (60*HZ) about possible syn-flood? It really floods dmesg. Is there something dengerous? I have suggestion to turn off printk about sending tcp cookie each 1 second.

It is handled exactly like other printks in the networking path,
e.g. receipt of tcp wscale == 15.

Why does this need special treatment?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html