| 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
| ||
|
Date: Mon, 24 Feb 2014 18:04:26 -0500 (EST) From: David Miller <davem@...emloft.net> To: dcbw@...hat.com Cc: mcgrof@...not-panic.com, zoltan.kiss@...rix.com, netdev@...r.kernel.org, xen-devel@...ts.xenproject.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org, kaber@...sh.net Subject: Re: [RFC v2 2/4] net: enables interface option to skip IP From: Dan Williams <dcbw@...hat.com> Date: Mon, 24 Feb 2014 12:22:00 -0600 > In the future I expect more people will want to disable IPv4 as > they move to IPv6. I definitely don't. I've been lightly following this conversation and I have to say a few things. disable_ipv6 was added because people wanted to make sure their machines didn't generate any ipv6 traffic because "ipv6 is not mature", "we don't have our firewalls configured to handle that kind of traffic" etc. None of these things apply to ipv4. And if you think people will go to ipv6 only, you are dreaming. Name a provider of a major web sitewho will go to strictly only providing an ipv6 facing site? Only an idiot who wanted to lose significiant nunbers of page views and traffic would do that, so ipv4 based connectivity will be universally necessary forever. I think disable_ipv4 is absolutely a non-starter. -- 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