On Wed, Sep 16, 2009 at 10:03 AM, Bernd Zeimetz <[email protected]> wrote:
> This bug should *NOT* be closed. That's debatable. I believe it should be closed and I closed it. > Getting a deprecation warning for a simple and common use of > iptables is a bug somewhere, either in iptables or the kernel. You certainly can use iptables to initiate events that automatically insert the nf_conntrack kernel module into the kernel, which gives the warning. You can get the same result by manually inserting the nf_conntrack kernel module. > And I really fail to understand why the iptables maintainer thinks it is > useful in any way to tag this bug wontfix without any comment at all. I thought about this deeply in May for some twenty seconds. I then commented, retitled the bug report and closed it. The re-openings, additional closing, retitling, package shifting, impassioned tear jerking over system security concerns, inane suggestion of changing system defaults, etc have done nothing to change my mind about my initial response. It's a kernel warning. It's not a kernel bug. It's not an iptables bug. > Are people supposed to live with that deprecation warning forever? It suspect it will be addressed eventually. > I'd expect that Debian provides useful defaults, running in such a > warning is not useful. Changing the default in question does not affect the warning. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
