Return-path: Received: from mail-bl2on0117.outbound.protection.outlook.com ([65.55.169.117]:20640 "EHLO na01-bl2-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932943AbaLBTmR (ORCPT ); Tue, 2 Dec 2014 14:42:17 -0500 Received: by mail-ob0-f174.google.com with SMTP id nt9so3393397obb.33 for ; Tue, 02 Dec 2014 11:42:07 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <547E1485.40302@broadcom.com> References: <20141202003143.GA11546@tuxdriver.com> <547E1485.40302@broadcom.com> From: Eric Schultz Date: Tue, 2 Dec 2014 13:41:47 -0600 Message-ID: (sfid-20141202_204226_007772_02A5E025) Subject: Re: New FCC requirements and Linux Wifi To: Arend van Spriel CC: "John W. Linville" , Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org List-ID: Arend, When I mean Linux hardware being hackable, I was referring to the ability of users to modify and replace the operating system as appropriate. As for hardware companies, it would be mostly OEMs. I'll send details off list today probably about the exact issues related to the the rule. Thanks, Eric On Tue, Dec 2, 2014 at 1:35 PM, Arend van Spriel wrote: > On 12/02/14 01:31, John W. Linville wrote: >> >> On Mon, Dec 01, 2014 at 04:27:25PM -0600, Eric Schultz wrote: >>> >>> All, >>> >>> I work for the prpl Foundation, an open source foundation organized by >>> a number of companies, most related to MIPS. One project we work with >>> externally is the OpenWrt project. Recently one of our members >>> mentioned a new FCC requirement (described in FCC publication 594280) >>> which requires wifi hardware devices to restrict modifications in ways >>> that were not previously required. Some of the suggestions the company >>> had internally for complying would be to use features like Secure Boot >>> and other types of DRM-like mechanisms to prevent routers from being >>> modified. This obviously would be quite bad for the OpenWrt community >>> (and the embedded Linux community as a whole) so we agreed as a group >>> to try to provide hardware companies with a way of complying without >>> harming the community. >>> >>> I'm looking to find individuals (and other companies!) interested in >>> working with myself and the foundation, companies, the OpenWrt >>> community and eventually regulators to provide guidance to hardware >>> companies on how to best comply with these rules. If you're interested >>> in getting involved or just would like to know more, please get in >>> touch with me. We want to make sure that routers and related embedded >>> Linux hardware is hackable and we could use all the help we could get. >>> >>> Thanks and I look forward to working with you, >>> >>> Eric >> >> >> Eric, >> >> Obviously, I would be interested in hearing more. I suspect there >> are others on the list that will be interested as well... > > > I think so too. Just not sure what "Linux hardware is hackable" really means > here. Well, I guess I mean to say: tell me more. I guess with hardware > companies you mean OEMs here, right? > > Regards, > Arend -- Eric Schultz, Community Manager, prpl Foundation http://www.prplfoundation.org eschultz@prplfoundation.org cell: 920-539-0404 skype: ericschultzwi @EricPrpl