netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Ketrenos <jketreno@linux.intel.com>,
	NetDev <netdev@vger.kernel.org>,
	linux-kernel@vger.kernel.org, okir@suse.de
Subject: Re: [Announce] Intel PRO/Wireless 3945ABG Network Connection
Date: Sun, 26 Feb 2006 00:58:02 +0000	[thread overview]
Message-ID: <1140915482.23286.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20060225084139.GB22109@infradead.org>

On Sad, 2006-02-25 at 08:41 +0000, Christoph Hellwig wrote:
> the regualatory problems are not true.  

They are although the binary interpretation isn't AFAIK from law but
from lawyers. The same is actually true in much of the EU. The actual
requirement is that the transmitting device must be reasonably
tamperproof. Some of the lawyers have decided that for a software radio
tamperproof means "binary".

Thats pretty dumb but given the hardware variant of this is "seal
anything adjustible in plastic gunge" you can see the logic at work -
and it *will* help make the product tamperproof to end users. Remember
Christoph you are not an "end user" any more than hardware like that is
designed to proof against a person who can use a scope and solder
surface mount components.

Now a smart vendor would have put MD5 sum checking into the chip so you
can only load register sets for the transmitter as a block and that
block is loaded such that

	[Data] + Secret known only to chip = MD5sum with data

or a similar cookie signing scheme. Replay attacks don't matter here so
that should be sufficient.

  parent reply	other threads:[~2006-02-26  0:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-24 22:29 [Announce] Intel PRO/Wireless 3945ABG Network Connection James Ketrenos
2006-02-24 23:34 ` Dax Kelson
2006-02-24 23:48 ` Jeff V. Merkey
2006-02-25 13:26   ` Michael Buesch
2006-02-25  8:41 ` Christoph Hellwig
2006-02-25 10:49   ` Gene Heskett
2006-02-25 10:53     ` Christoph Hellwig
2006-02-25 11:19       ` Gene Heskett
2006-02-25 13:19         ` Michael Buesch
2006-02-26  1:09         ` Stephen Evanchik
2006-02-25 12:29       ` Stefan Rompf
2006-02-25 14:19     ` Jan Engelhardt
2006-02-25 22:07       ` Matthieu CASTET
2006-02-25 22:19         ` John Stoffel
2006-02-25 22:28           ` matthieu castet
2006-02-25 22:47             ` Larry Finger
2006-02-26 20:20           ` Alejandro Bonilla
2006-02-26  0:58   ` Alan Cox [this message]
2006-02-27 17:10     ` Christoph Hellwig
2006-02-27 17:34       ` Stephen Hemminger
2006-03-03 20:04       ` Kasper Sandberg
2006-03-03 20:31         ` Jeff Garzik
2006-02-26 17:54 ` Pavel Machek

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=1140915482.23286.6.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=hch@infradead.org \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=okir@suse.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 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).