From: Stefano Brivio <stefano.brivio@polimi.it>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: RFC: Regulatory info in mac80211
Date: Thu, 7 Jun 2007 09:10:40 +0200 [thread overview]
Message-ID: <20070607091040.2b2f1d00@morte> (raw)
In-Reply-To: <4665CCE7.5090409@lwfinger.net>
On Tue, 05 Jun 2007 15:51:51 -0500
Larry Finger <Larry.Finger@lwfinger.net> wrote:
> 3. There should be some sort of checking to verify that the database has
> not been hacked to modify transmission power, etc. in an illegal manner.
> Obviously, no foolproof means of enforcing this does not exist; however,
> we should prevent the crudest form of modifications.
Why should this be enforced at all? What the Linux kernel has to do with
enforcing legality?
I see implementation of regulatory information in mac80211 as a convenient
way in order to avoid issues for the end user. Those issues includes:
1) violating the regulatory domain compliance without noticing;
2) losing time in order to get around domain compliance checks, when
this is done with perfect consciousness.
--
Ciao
Stefano
next prev parent reply other threads:[~2007-06-07 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 20:51 RFC: Regulatory info in mac80211 Larry Finger
2007-06-05 23:35 ` Luis R. Rodriguez
2007-06-05 23:54 ` Iñaky Pérez-González
2007-06-06 4:18 ` Dan Williams
2007-06-07 7:10 ` Stefano Brivio [this message]
2007-06-07 18:52 ` Luis R. Rodriguez
2007-06-07 19:27 ` stefano.brivio
2007-06-07 21:35 ` Luis R. Rodriguez
2007-06-09 3:50 ` Daniel Drake
2007-06-11 2:44 ` Larry Finger
-- strict thread matches above, loose matches on Subject: below --
2007-06-06 10:00 Joerg Pommnitz
2007-06-06 11:41 ` Johannes Berg
2007-06-06 13:46 ` Larry Finger
2007-06-06 12:14 Joerg Pommnitz
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=20070607091040.2b2f1d00@morte \
--to=stefano.brivio@polimi.it \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).