From: "John W. Linville" <linville@tuxdriver.com>
To: Kel Modderman <kel@otaku42.de>
Cc: debian-devel@lists.debian.org,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: [renamed] Debian crda?
Date: Wed, 25 Mar 2009 14:12:32 -0400 [thread overview]
Message-ID: <20090325181232.GA6882@tuxdriver.com> (raw)
In-Reply-To: <200903260345.30678.kel@otaku42.de>
On Thu, Mar 26, 2009 at 03:45:30AM +1000, Kel Modderman wrote:
> On Wednesday 25 March 2009 17:39:03 Paul Wise wrote:
> > On Wed, Mar 25, 2009 at 4:09 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> >
> > > Last time I poked them it seemed it was not easy to figure out how to
> > > deal with, if at all, the optional but recommended RSA signature stuff
> > > [1] with the DFSG.
> > >
> > > [1] http://wireless.kernel.org/en/developers/Regulatory#RSADigitalSignature
> >
> > What is the percieved DFSG/RSA conflict? I can't detect any based on
> > that section of the page.
>
> Hi Paul,
>
> By default the upstream wireless-regdb tarball contains and installs a
> pre-built wireless regulatory information binary signed by John Linville's
> openssl snakeoil. It is my understanding that in Debian we would prefer to
> build the binary from its source code. That presents a problem because CRDA
> expects to see John Linville's openssl stuff. One way to work around this
> is to munge CRDA and regdb together, generate our own openssl stuff and build
> CRDA and wireless-redb at the same time. Another way to go is to do away with
> the openssl stuff during build altogether, but Luis doesn't like that, and the
> build system's need patching to support it last time I checked.
You could also patch-in support for your own signing key, provided
that would comply with whatever policies Debian has about signing keys.
Hth...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-03-25 18:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 7:09 [renamed] Debian crda? Luis R. Rodriguez
[not found] ` <e13a36b30903250039h55c8a01cg9dada9256bc8b1ae@mail.gmail.com>
2009-03-25 7:47 ` Luis R. Rodriguez
2009-03-25 7:51 ` Luis R. Rodriguez
2009-03-25 11:34 ` Evgeni Golov
2009-03-25 17:37 ` Kel Modderman
2009-03-25 17:40 ` Johannes Berg
2009-03-25 17:41 ` Luis R. Rodriguez
2009-03-25 18:42 ` Kel Modderman
[not found] ` <e13a36b30903251203v7c53fb20g64bf61e4e433377@mail.gmail.com>
2009-03-25 20:25 ` Luis R. Rodriguez
2009-03-25 20:27 ` Luis R. Rodriguez
[not found] ` <e13a36b30903252008i72caad77y32e31f625b7cb842@mail.gmail.com>
2009-03-26 4:19 ` Luis R. Rodriguez
2009-03-26 4:59 ` Paul Wise
2009-03-27 4:00 ` Luis R. Rodriguez
2009-03-25 17:45 ` Kel Modderman
2009-03-25 18:12 ` John W. Linville [this message]
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=20090325181232.GA6882@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=debian-devel@lists.debian.org \
--cc=kel@otaku42.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.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 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.