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-next>] [day] [month] [year] [list]
Date:	Tue, 03 Mar 2009 21:37:10 -0500
From:	Brian Haley <brian.haley@...com>
To:	David Miller <davem@...emloft.net>
CC:	Andrey Borzenkov <arvidjaar@...l.ru>,
	Vladislav Yasevich <vladislav.yasevich@...com>,
	Chuck Lever <chuck.lever@...cle.com>,
	Theodore Tso <tytso@....edu>, Valdis.Kletnieks@...edu,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	bonding-devel@...ts.sourceforge.net,
	"J.A. Magallón" 
	<jamagallon@....com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jay Vosburgh <fubar@...ibm.com>
Subject: [PATCH 0/2] Bonding: fix IPv6 module requirement regression


These patches fix the Bonding module's requirement to have the IPv6
module loaded and configured by creating a new "disable" module parameter
value for ipv6.ko.  This allows users who do not want any IPv6 addresses
or sockets to be created to disable IPv6 support, while still loading
the module and making it's symbols available.  This can be specified in
/etc/modprobe.conf (or similar) with "options ipv6 disable=1".

I've verified that Bonding, SCTP, Sunrpc and DCCP will still load, however
dccp_ipv6 will not load when disable=1 - I believe this is ok as
IPv6 won't work anyways.


  Documentation/networking/ipv6.txt |   35 +++++++++++++++++++++++++++++++++++
  net/ipv6/af_inet6.c               |   22 ++++++++++++++++------
  net/sctp/protocol.c               |   11 ++++++++---
  3 files changed, 59 insertions(+), 9 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ