| 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
| ||
|
Message-Id: <20120114.115604.2101782124431552110.davem@davemloft.net> Date: Sat, 14 Jan 2012 11:56:04 -0800 (PST) From: David Miller <davem@...emloft.net> To: dvhart@...ux.intel.com Cc: linux-kernel@...r.kernel.org, arjan@...ux.intel.com, alan@...ux.intel.com, tomoya.rohm@...il.com, jeffrey.t.kirsher@...el.com, paul.gortmaker@...driver.com, jdmason@...zu.us, netdev@...r.kernel.org Subject: Re: [PATCH] pch_gbe: Use a randomly generated MAC instead of failing probe From: Darren Hart <dvhart@...ux.intel.com> Date: Sat, 14 Jan 2012 07:54:27 -0800 >> Please correct any hardware that hasn't shipped yet or is alpha/beta >> hardware in testing, so that we don't need stuff like this. > > I saw that the use of random_ether_addr is fairly prevalent, and > attempted a roughly similar sort of approach to others I had seen. Do > you consider all of those to be "necessary evils" or are there > legitimate situations for its use? > > In any case, with existing hardware out there that is unusable with the > current pch_gbe driver, can we consider this workaround for inclusion? I fear that people are just going to add this random MAC stuff way too easily, it's a spreading disease. Ship functional hardware instead. -- 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