All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Steve deRosier <derosier@gmail.com>,
	Simon Wunderlich <sw@simonwunderlich.de>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	ath10k@lists.infradead.org, ath9k-devel@qca.qualcomm.com,
	linux-wireless@vger.kernel.org,
	Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>,
	Julian Calaby <julian.calaby@gmail.com>
Subject: Re: [v2,1/3] ath9k: Support channels in licensed bands
Date: Tue, 18 Apr 2017 10:09:59 -0700	[thread overview]
Message-ID: <d4acedac-e28c-4c1c-d112-40557d52f3a2@candelatech.com> (raw)
In-Reply-To: <CALLGbRK2d1wZpfLnXu_UDWxVPA9LvejFyEFpzMub56uLH0+DTw@mail.gmail.com>

On 04/18/2017 09:33 AM, Steve deRosier wrote:
> Hi,
>
> On Tue, Apr 18, 2017 at 7:50 AM, Simon Wunderlich <sw@simonwunderlich.de <mailto:sw@simonwunderlich.de>> wrote:
>
>     Hi,
>
>     On Tuesday, April 18, 2017 2:36:54 PM CEST Kalle Valo wrote:
>     > Simon Wunderlich <sw@simonwunderlich.de <mailto:sw@simonwunderlich.de>> wrote:
>     > > From: Ben Greear <greearb@candelatech.com <mailto:greearb@candelatech.com>>
>     > >
>     > > Many chips support channels in licensed bands. Add support for those,
>     > > along with a corresponding kernel config option to disable them by
>
> ...
>
>     > I am not sure that we should support unlicensed bands in Linux and hence
>     > hesitant to apply these. My view is that due to regulatory restrictions we
>     > should not make it too easy to use unlicensed bands. But I'm open for
>     > discussion, this is a challenging area and my knowledge here is limited.
>
> ...
>
>
>     In my personal view, we have quite a few obstacles which I consider "enough",
>     but would be interesting to hear others opinions ...
>
>
> I'll throw in my 2-cents. This patch is treading on very dangerous ground. I can't speak to other regulatory environments, but at least the FCC is cracking down
> on even the possibility that anyone can operate a WiFi device outside the regulatory bounds.

These patches make it slightly easier to use the licensed bands, but no one
can accidentally use them due to the regdb and other constaints in these
patches.

So, I don't think these patches offer any fundamental new vulnerability
that should concern the FCC.

After all, someone who really wants to do evil can find and apply the patches
without undue effort, and it could easily be that those applying the patches would
then make it even easier to abuse the new channels due to laziness or poor coding
choices.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Steve deRosier <derosier@gmail.com>,
	Simon Wunderlich <sw@simonwunderlich.de>
Cc: Julian Calaby <julian.calaby@gmail.com>,
	linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
	ath10k@lists.infradead.org,
	Mathias Kretschmer <mathias.kretschmer@fit.fraunhofer.de>,
	Kalle Valo <kvalo@codeaurora.org>
Subject: Re: [v2,1/3] ath9k: Support channels in licensed bands
Date: Tue, 18 Apr 2017 10:09:59 -0700	[thread overview]
Message-ID: <d4acedac-e28c-4c1c-d112-40557d52f3a2@candelatech.com> (raw)
In-Reply-To: <CALLGbRK2d1wZpfLnXu_UDWxVPA9LvejFyEFpzMub56uLH0+DTw@mail.gmail.com>

On 04/18/2017 09:33 AM, Steve deRosier wrote:
> Hi,
>
> On Tue, Apr 18, 2017 at 7:50 AM, Simon Wunderlich <sw@simonwunderlich.de <mailto:sw@simonwunderlich.de>> wrote:
>
>     Hi,
>
>     On Tuesday, April 18, 2017 2:36:54 PM CEST Kalle Valo wrote:
>     > Simon Wunderlich <sw@simonwunderlich.de <mailto:sw@simonwunderlich.de>> wrote:
>     > > From: Ben Greear <greearb@candelatech.com <mailto:greearb@candelatech.com>>
>     > >
>     > > Many chips support channels in licensed bands. Add support for those,
>     > > along with a corresponding kernel config option to disable them by
>
> ...
>
>     > I am not sure that we should support unlicensed bands in Linux and hence
>     > hesitant to apply these. My view is that due to regulatory restrictions we
>     > should not make it too easy to use unlicensed bands. But I'm open for
>     > discussion, this is a challenging area and my knowledge here is limited.
>
> ...
>
>
>     In my personal view, we have quite a few obstacles which I consider "enough",
>     but would be interesting to hear others opinions ...
>
>
> I'll throw in my 2-cents. This patch is treading on very dangerous ground. I can't speak to other regulatory environments, but at least the FCC is cracking down
> on even the possibility that anyone can operate a WiFi device outside the regulatory bounds.

These patches make it slightly easier to use the licensed bands, but no one
can accidentally use them due to the regdb and other constaints in these
patches.

So, I don't think these patches offer any fundamental new vulnerability
that should concern the FCC.

After all, someone who really wants to do evil can find and apply the patches
without undue effort, and it could easily be that those applying the patches would
then make it even easier to abuse the new channels due to laziness or poor coding
choices.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2017-04-18 17:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 13:30 [PATCH v2 0/3] Channels in licensed bands, noise floor override Simon Wunderlich
2017-03-23 13:30 ` Simon Wunderlich
2017-03-23 13:30 ` [PATCH v2 1/3] ath9k: Support channels in licensed bands Simon Wunderlich
2017-03-23 13:30   ` Simon Wunderlich
2017-04-18 14:36   ` [v2,1/3] " Kalle Valo
2017-04-18 14:36   ` Kalle Valo
     [not found]   ` <20170418143654.8AC0A60FAA@smtp.codeaurora.org>
2017-04-18 14:50     ` Simon Wunderlich
2017-04-18 14:50       ` Simon Wunderlich
2017-04-18 16:38       ` Steve deRosier
2017-04-18 16:38         ` Steve deRosier
     [not found]       ` <CALLGbRK2d1wZpfLnXu_UDWxVPA9LvejFyEFpzMub56uLH0+DTw@mail.gmail.com>
2017-04-18 17:09         ` Ben Greear [this message]
2017-04-18 17:09           ` Ben Greear
2017-04-21 11:29           ` Simon Wunderlich
2017-04-21 11:29             ` Simon Wunderlich
2017-04-21 12:40             ` Mathias Kretschmer
2017-04-21 12:40               ` Mathias Kretschmer
2017-05-09 12:57               ` Simon Wunderlich
2017-05-09 12:57                 ` Simon Wunderlich
2017-05-09 17:50                 ` Adrian Chadd
2017-05-09 17:50                   ` Adrian Chadd
     [not found]                   ` <CAKR_QV+0cPXbiScO3cS52R97o=wGh4+zgmqaRM7QbotmEJD51Q@mail.gmail.com>
2017-05-10 16:17                     ` Ben Greear
2017-05-10 16:17                       ` Ben Greear
2017-05-11 11:38                 ` Kalle Valo
2017-05-11 11:38                   ` Kalle Valo
2017-05-12 14:12                   ` Ben Greear
2017-05-12 14:12                     ` Ben Greear
2017-05-12 19:21                     ` Steve deRosier
2017-05-12 19:21                       ` Steve deRosier
2017-05-12 19:44                       ` Ben Greear
2017-05-12 19:44                         ` Ben Greear
2017-05-13 12:12                       ` Arend Van Spriel
2017-05-13 12:12                         ` Arend Van Spriel
2017-03-23 13:30 ` [PATCH v2 2/3] ath10k: add support for " Simon Wunderlich
2017-03-23 13:30   ` Simon Wunderlich
2017-03-23 13:30 ` [PATCH v2 3/3] ath9k: add noise floor override option Simon Wunderlich
2017-03-23 13:30   ` Simon Wunderlich
2017-04-19 14:08   ` [v2,3/3] " Kalle Valo
2017-04-19 14:08     ` Kalle Valo

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

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

  git send-email \
    --in-reply-to=d4acedac-e28c-4c1c-d112-40557d52f3a2@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=derosier@gmail.com \
    --cc=julian.calaby@gmail.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mathias.kretschmer@fit.fraunhofer.de \
    --cc=sw@simonwunderlich.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.