netdev - Re: disabling ipv6 (when ipv6 module is already loaded or built in)

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]

Message-Id: <20110325.155657.193733904.davem@davemloft.net>
Date:	Fri, 25 Mar 2011 15:56:57 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	a.miskiewicz@...il.com
Cc:	brian.haley@...com, netdev@...r.kernel.org
Subject: Re: disabling ipv6 (when ipv6 module is already loaded or built in)

From: Arkadiusz Miskiewicz <a.miskiewicz@...il.com>
Date: Fri, 25 Mar 2011 23:53:06 +0100

> The whole problem is that socket(AF_INET6,...) is allowed. If setting 
> net.ipv6.conf.all.disable_ipv6=1 would also prevent such socket() from 
> succeeding then everything would be fine.

You have to make this setting before the module loads, once we register
the protocol handlers (which is what allows socket() to succeed) the
cat is out of the bag.

If even just one socket exists, we can't perform the steps necessary
to block new ones.

That's why you have to use the module option, and it is the only way
to block this class of operations.
--
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