Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Eric Schultz <eschultz@prplfoundation.org>
To: <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] New FCC requirements and CeroWrt
Date: Tue, 9 Dec 2014 11:11:10 -0600	[thread overview]
Message-ID: <CAMkzgA5cws8AM3iWe9geAkbL3aKF414wQT0i1=02AQjuXsRjRA@mail.gmail.com> (raw)

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 at
http://wiki.prplfoundation.org/wiki/Complying_with_FCC_rules_on_5ghz_wifi)
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 ecosystem
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 are hackable
and we could use all the help we can get.

Thanks and I look forward to working with you,

Eric

-- 
Eric Schultz, Community Manager, prpl Foundation
http://www.prplfoundation.org
eschultz@prplfoundation.org
cell: 920-539-0404
skype: ericschultzwi
@EricPrpl

             reply	other threads:[~2014-12-09 17:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09 17:11 Eric Schultz [this message]
2014-12-09 17:49 ` Dave Taht
2014-12-09 18:56   ` Eric Schultz
2014-12-09 20:14     ` David Lang
2014-12-09 20:32       ` Dave Taht
2014-12-09 20:46         ` David Lang
2014-12-09 20:34       ` Eric Schultz
2014-12-09 21:01         ` David Lang
2014-12-09 21:02         ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMkzgA5cws8AM3iWe9geAkbL3aKF414wQT0i1=02AQjuXsRjRA@mail.gmail.com' \
    --to=eschultz@prplfoundation.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox