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: <4D8CF970.7020601@hp.com>
Date:	Fri, 25 Mar 2011 16:22:08 -0400
From:	Brian Haley <brian.haley@...com>
To:	Arkadiusz Miskiewicz <a.miskiewicz@...il.com>
CC:	netdev@...r.kernel.org
Subject: Re: disabling ipv6 (when ipv6 module is already loaded or built in)

On 03/25/2011 01:17 PM, Arkadiusz Miskiewicz wrote:
> 
> Hi,
> 
> There are two options for disabling some ipv6 functionality in ipv6 module - 
> disable and disable_ipv6. The second option is also available as sysctl and 
> can be switched runtime.
> 
> First is nicer because it also prevents apps from creating sockets by using 
> socket(AF_INET6, ...). Various apps use AF_INET6 socket creation to deterine 
> if ipv6 is supported on the system. Unfortunately "disable" one doesn't exist 
> as sysctl and this is a problem.
> 
> Is it possible to make "disable" sysctl option, too? Currently there is no 
> runtime way to disable ipv6 (or I'm unaware of such way).

Not really, the module parameter causes IPv6 to be loaded just enough to
allow other modules that rely on it to load, but it never registers
any of the protocol handlers, sysctls, tables, etc. to make it usable.
And the IPv6 module isn't unloadable, so you have to reboot to change
this setting.

When there are no addresses it's not very usable since you can't send
out packets...

-Brian
--
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