From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Davide Pesavento <davidepesa@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Tim Gardner <tim.gardner@canonical.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: crda packaging
Date: Mon, 20 Oct 2008 07:04:38 -0700 [thread overview]
Message-ID: <20081020140438.GD9035@tesla> (raw)
In-Reply-To: <2da21fe50810201336r29ed4e83g18d57e6d01b97349@mail.gmail.com>
On Mon, Oct 20, 2008 at 01:36:27PM -0700, Davide Pesavento wrote:
> 2008/10/20 Luis R. Rodriguez <mcgrof@gmail.com>:
> > We just need to get this git tree created. What crda will need though
> > is to wget the RSA public key so it can be built with support for new
> > arbitrary updates to the binary db. Give us a few days, we'll get this
> > setup.
> >
>
> I'm not sure I can follow you here. This is what I understood so far:
>
> (1) Someone (e.g. John Linville) creates a RSA key pair and puts the
> public key in a public place (e.g. linuxwireless.org website).
Sure, although I'd use "wireless.kernel.org" from here on as we have no
control over linuxwireless.org and the domain owner didn't want to give us
ownership of it so we cannot be sure it'll always be updated.
> (2) John "compiles" db.txt into its binary form (regulatory.bin),
> signs it with his private key and makes it publicly available
> somewhere (e.g. again linuxwireless.org).
ACK
> (3) Packagers create a package for the crda daemon alone, and a
> package containing regulatory.bin and the public part of the key pair
> used to sign it.
The public key will need to be wget'd to build crda binary as the public
key is built in as part of the binary.
> (4) When the regulatory database is updated, John releases a new
> version by "compiling" and signing it again.
ACK
Luis
next prev parent reply other threads:[~2008-10-20 21:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 15:57 crda packaging Davide Pesavento
2008-10-20 1:28 ` Luis R. Rodriguez
2008-10-20 20:36 ` Davide Pesavento
2008-10-20 14:04 ` Luis R. Rodriguez [this message]
2008-10-20 21:48 ` Davide Pesavento
2008-10-20 22:15 ` Luis R. Rodriguez
2008-10-20 22:39 ` Davide Pesavento
2008-10-20 15:43 ` Luis R. Rodriguez
2008-10-25 9:54 ` Davide Pesavento
2008-10-28 1:38 ` Luis R. Rodriguez
2008-10-20 22:16 ` Luis R. Rodriguez
2008-11-16 20:58 ` Davide Pesavento
2008-11-17 20:27 ` Luis R. Rodriguez
2008-11-17 22:21 ` Luis R. Rodriguez
2008-11-17 22:25 ` Luis R. Rodriguez
2008-11-23 18:40 ` Davide Pesavento
2008-11-24 17:36 ` Luis R. Rodriguez
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=20081020140438.GD9035@tesla \
--to=lrodriguez@atheros.com \
--cc=davidepesa@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=tim.gardner@canonical.com \
/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).