From: Ed W <lists@wildgooses.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Mr Dash Four <mr.dash.four@googlemail.com>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
netfilter@vger.kernel.org
Subject: Re: ipset, IP6_NF_IPTABLES
Date: Tue, 17 May 2011 14:04:20 +0100 [thread overview]
Message-ID: <4DD27254.1090706@wildgooses.com> (raw)
In-Reply-To: <fbc9abc624824c8e6f973c342e81fe51@visp.net.lb>
On 17/05/2011 12:14, Denys Fedoryshchenko wrote:
> Especially it is a problem for source based distributions, like gentoo,
I know there was a debate about this on the gentoo-hardened list
recently, but my opinion is that one needs to start "enabling" (as in
it's installed/compiled in) IPV6 code on all systems ASAP and start
flushing out problems. That said I think it's also fair to lock
down/disable/minimise your use of the IPV6 to whatever is appropriate to
your environment/requirements, but having the code there, compiled into
production systems and starting to test it would seem to be very prudent
right now?
Just add USE="+ipv6" to your make.conf, "emerge --newuse -uvDkp world"
and off you go...
Good luck
Ed W
next prev parent reply other threads:[~2011-05-17 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 7:49 ipset, IP6_NF_IPTABLES Denys Fedoryshchenko
2011-05-17 8:07 ` Jozsef Kadlecsik
2011-05-17 11:07 ` Mr Dash Four
2011-05-17 11:14 ` Denys Fedoryshchenko
2011-05-17 11:33 ` Jozsef Kadlecsik
2011-05-17 16:31 ` Jozsef Kadlecsik
2011-05-17 13:04 ` Ed W [this message]
2011-05-17 13:18 ` Denys Fedoryshchenko
2011-05-17 11:25 ` Jozsef Kadlecsik
2011-05-17 15:18 ` Mr Dash Four
2011-05-17 16:34 ` Jozsef Kadlecsik
2011-05-17 16:55 ` Denys Fedoryshchenko
2011-05-17 17:25 ` Jozsef Kadlecsik
2011-05-17 18:34 ` Mr Dash Four
2011-05-17 21:50 ` Mr Dash Four
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD27254.1090706@wildgooses.com \
--to=lists@wildgooses.com \
--cc=denys@visp.net.lb \
--cc=kadlec@blackhole.kfki.hu \
--cc=mr.dash.four@googlemail.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.