[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081214200353.GA2994@redhat.com>
Date: Sun, 14 Dec 2008 15:03:53 -0500
From: Dave Jones <davej@...hat.com>
To: Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>
Cc: Jan Engelhardt <jengelh@...ozas.de>,
David Miller <davem@...emloft.net>, ajax@...hat.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
netfilter-devel@...r.kernel.org, Patrick McHardy <kaber@...sh.net>
Subject: Re: [PATCH] net: Remove a noisy printk
On Sun, Dec 14, 2008 at 06:09:17PM +0100, Jozsef Kadlecsik wrote:
> > >> @@ -147,8 +147,6 @@ static unsigned int ipv4_conntrack_local(unsigned int hooknum,
> > >> /* root is playing with raw sockets. */
> > >> if (skb->len < sizeof(struct iphdr) ||
> > >> ip_hdrlen(skb) < sizeof(struct iphdr)) {
> > >> - if (net_ratelimit())
> > >> - printk("ipt_hook: happy cracking.\n");
> > >> return NF_ACCEPT;
> > >> }
> > >> return nf_conntrack_in(dev_net(out), PF_INET, hooknum, skb);
> >
> > I think this change is ok.
>
> In a >normal< system one usually does not use raw sockets. So if a root
> process do use raw socket, at least netfilter sends a notification and
> there's a chance that someone take notice it by checking the kernel logs.
'normal' systems are irrelevant here. This message is triggerable remotely.
Even though it's ratelimited, anyone can flood another boxes logs by
sending enough packets.
The message is also utterly useless. What kind of action would you take
to a few gigabytes of "ipt_hook: happy cracking.\n" ?
There's no IP address logged, or any other useful information.
Dave
--
http://www.codemonkey.org.uk
--
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
Powered by blists - more mailing lists