crda packaging

crda packaging

[Davide Pesavento]

2008/9/28 Luis R. Rodriguez <mcgrof@gmail.com>:
> On Sat, Sep 27, 2008 at 9:59 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
>> 2008/9/16 Johannes Berg <johannes@sipsolutions.net>:
>>> Anyone want to pick it up for the various distros?
>>
>> I've written an ebuild for Gentoo and attached it to bug #238879.
>> https://bugs.gentoo.org/show_bug.cgi?id=238879
>
> Would you be able to start packaging crda as well? It'll be very good
> to have this by 2.6.28 and if you guys have a compat-wireless, it will
> soon require it (by 2.6.29).
>

I'll be glad to help ;)

> The regulatory.bin and the rsa public key will soon be posted on some
> place on John Linville's web space somewhere, so that'll change soon I
> hope.
>

Do you think the regulatory database should be split from the package
that contains the crda daemon? If so, regulatory.bin should be
versioned as well...

Re: crda packaging

[Luis R. Rodriguez]

On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
> 2008/9/28 Luis R. Rodriguez <mcgrof@gmail.com>:
>> On Sat, Sep 27, 2008 at 9:59 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
>>> 2008/9/16 Johannes Berg <johannes@sipsolutions.net>:
>>>> Anyone want to pick it up for the various distros?
>>>
>>> I've written an ebuild for Gentoo and attached it to bug #238879.
>>> https://bugs.gentoo.org/show_bug.cgi?id=238879
>>
>> Would you be able to start packaging crda as well? It'll be very good
>> to have this by 2.6.28 and if you guys have a compat-wireless, it will
>> soon require it (by 2.6.29).
>>
>
> I'll be glad to help ;)

Excellent, thanks :)

>> The regulatory.bin and the rsa public key will soon be posted on some
>> place on John Linville's web space somewhere, so that'll change soon I
>> hope.
>>
>
> Do you think the regulatory database should be split from the package
> that contains the crda daemon? If so, regulatory.bin should be
> versioned as well...

Yes, absolutely, the idea is to split db.txt into a separate git tree
too actually so that should help with keeping track of changes
separately and thinking of them separately.

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.

  Luis

Re: crda packaging

[Davide Pesavento]

2008/10/20 Luis R. Rodriguez <mcgrof@gmail.com>:
> On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
>> 2008/9/28 Luis R. Rodriguez <mcgrof@gmail.com>:
>>> The regulatory.bin and the rsa public key will soon be posted on some
>>> place on John Linville's web space somewhere, so that'll change soon I
>>> hope.
>>
>> Do you think the regulatory database should be split from the package
>> that contains the crda daemon? If so, regulatory.bin should be
>> versioned as well...
>
> Yes, absolutely, the idea is to split db.txt into a separate git tree
> too actually so that should help with keeping track of changes
> separately and thinking of them separately.
>

Great!

> 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).
(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).
(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.
(4) When the regulatory database is updated, John releases a new
version by "compiling" and signing it again.

Thanks,
Davide

Re: crda packaging

[Luis R. Rodriguez]

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

Re: crda packaging

[Davide Pesavento]

2008/10/20 Luis R. Rodriguez <lrodriguez@atheros.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.
>

Ok.

>> (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.
>

Ah, right. This is the point I forgot, thanks for your explanation.
This is not a problem for Gentoo ebuilds; I guess it isn't for other
distros as well.

>> (4) When the regulatory database is updated, John releases a new
>> version by "compiling" and signing it again.
>
> ACK
>
>  Luis
>

Regards,
Davide

Re: crda packaging

[Luis R. Rodriguez]

On Mon, Oct 20, 2008 at 2:48 PM, Davide Pesavento <davidepesa@gmail.com> wrote:

> Ah, right. This is the point I forgot, thanks for your explanation.
> This is not a problem for Gentoo ebuilds; I guess it isn't for other
> distros as well.

Ah you do the gentoo packaging?

>>> (4) When the regulatory database is updated, John releases a new
>>> version by "compiling" and signing it again.

BTW -- the reason I mentioned a separate git tree for db.txt is so
that we can handle releases of crda and the binary db separately.

  Luis

Re: crda packaging

[Davide Pesavento]

2008/10/21 Luis R. Rodriguez <lrodriguez@atheros.com>:
> On Mon, Oct 20, 2008 at 2:48 PM, Davide Pesavento <davidepesa@gmail.com> wrote:
>
>> Ah, right. This is the point I forgot, thanks for your explanation.
>> This is not a problem for Gentoo ebuilds; I guess it isn't for other
>> distros as well.
>
> Ah you do the gentoo packaging?
>

That's the idea. I'm not a gentoo developer (not yet at least), but I
can write an ebuild and submit it for inclusion into portage.
Do you need any other help?

>>>> (4) When the regulatory database is updated, John releases a new
>>>> version by "compiling" and signing it again.
>
> BTW -- the reason I mentioned a separate git tree for db.txt is so
> that we can handle releases of crda and the binary db separately.
>

Yeah, of course. This is the best solution I think.

Davide

Re: crda packaging

[Luis R. Rodriguez]

On Mon, Oct 20, 2008 at 03:39:21PM -0700, Davide Pesavento wrote:
> 2008/10/21 Luis R. Rodriguez <lrodriguez@atheros.com>:
> > On Mon, Oct 20, 2008 at 2:48 PM, Davide Pesavento <davidepesa@gmail.com> wrote:
> >
> >> Ah, right. This is the point I forgot, thanks for your explanation.
> >> This is not a problem for Gentoo ebuilds; I guess it isn't for other
> >> distros as well.
> >
> > Ah you do the gentoo packaging?
> >
> 
> That's the idea. I'm not a gentoo developer (not yet at least), but I
> can write an ebuild and submit it for inclusion into portage.
> Do you need any other help?

We just need iw and crda packeged up so that in itself is greatly
appreciated. Thanks.

  Luis

Re: crda packaging

[Davide Pesavento]

Only a couple of issues now remain in crda:

(1) crda needs <linux/nl80211.h>, thus a kernel source tree is
required to build it.
Solution: ship nl80211.h like iw does.

(2) `make verify` fails to validate the db signature if openssl is
selected instead of gcrypt.

Regards,
Davide

Re: crda packaging

[Luis R. Rodriguez]

On Sat, Oct 25, 2008 at 02:54:30AM -0700, Davide Pesavento wrote:
> Only a couple of issues now remain in crda:
> 
> (1) crda needs <linux/nl80211.h>, thus a kernel source tree is
> required to build it.
> Solution: ship nl80211.h like iw does.

Sure, I'll just steal Johannes' version.

> (2) `make verify` fails to validate the db signature if openssl is
> selected instead of gcrypt.

Hmm, I'll take a look if I can, right now am looking at interesection
though to automatically generate world and to use that later upstream
for 11d.

Thanks,

  Luis

Re: crda packaging

[Luis R. Rodriguez]

On Mon, Oct 20, 2008 at 2:48 PM, Davide Pesavento <davidepesa@gmail.com> wrote:

> Ah, right. This is the point I forgot, thanks for your explanation.
> This is not a problem for Gentoo ebuilds; I guess it isn't for other
> distros as well.

Ah you do the gentoo packaging?

>>> (4) When the regulatory database is updated, John releases a new
>>> version by "compiling" and signing it again.

BTW -- the reason I mentioned a separate git tree for db.txt is so
that we can handle releases of crda and the binary db separately.

  Luis

Re: crda packaging

[Davide Pesavento]

On Mon, Oct 20, 2008 at 02:28, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
>>
>> Do you think the regulatory database should be split from the package
>> that contains the crda daemon? If so, regulatory.bin should be
>> versioned as well...
>
> Yes, absolutely, the idea is to split db.txt into a separate git tree
> too actually so that should help with keeping track of changes
> separately and thinking of them separately.
>
> 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.
>
>  Luis
>

Any updates on this?

Davide

Re: crda packaging

[Luis R. Rodriguez]

On Sun, Nov 16, 2008 at 12:58:43PM -0800, Davide Pesavento wrote:
> On Mon, Oct 20, 2008 at 02:28, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> > On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
> >>
> >> Do you think the regulatory database should be split from the package
> >> that contains the crda daemon? If so, regulatory.bin should be
> >> versioned as well...
> >
> > Yes, absolutely, the idea is to split db.txt into a separate git tree
> > too actually so that should help with keeping track of changes
> > separately and thinking of them separately.
> >
> > 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.
> >
> >  Luis
> >
> 
> Any updates on this?

I think we'll have this done by the end of the day.

  Luis

Re: crda packaging

[Luis R. Rodriguez]

On Mon, Nov 17, 2008 at 12:27 PM, Luis R. Rodriguez
<lrodriguez@atheros.com> wrote:
> On Sun, Nov 16, 2008 at 12:58:43PM -0800, Davide Pesavento wrote:
>> On Mon, Oct 20, 2008 at 02:28, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>> > On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
>> >>
>> >> Do you think the regulatory database should be split from the package
>> >> that contains the crda daemon? If so, regulatory.bin should be
>> >> versioned as well...
>> >
>> > Yes, absolutely, the idea is to split db.txt into a separate git tree
>> > too actually so that should help with keeping track of changes
>> > separately and thinking of them separately.
>> >
>> > 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.
>> >
>> >  Luis
>> >
>>
>> Any updates on this?
>
> I think we'll have this done by the end of the day.

OK this is now done. We have a new git tree which John maintains for
the database:

git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git

All you need from that is the regulatory.bin, you don't need to run
make or anything, just cp the regulatory.bin to the preferred
location. Right now this is built into CRDA and its
/usr/lib/crda/regulatory.bin.

Then do a git pull on crda and try to build and let us know if you run
into any issues for packaging. The documentation on the
wireless.kernel.org wiki needs some good updating.

  Luis

Re: crda packaging

[Luis R. Rodriguez]

On Mon, Nov 17, 2008 at 2:21 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Mon, Nov 17, 2008 at 12:27 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
>> On Sun, Nov 16, 2008 at 12:58:43PM -0800, Davide Pesavento wrote:
>>> On Mon, Oct 20, 2008 at 02:28, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>>> > On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
>>> >>
>>> >> Do you think the regulatory database should be split from the package
>>> >> that contains the crda daemon? If so, regulatory.bin should be
>>> >> versioned as well...
>>> >
>>> > Yes, absolutely, the idea is to split db.txt into a separate git tree
>>> > too actually so that should help with keeping track of changes
>>> > separately and thinking of them separately.
>>> >
>>> > 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.
>>> >
>>> >  Luis
>>> >
>>>
>>> Any updates on this?
>>
>> I think we'll have this done by the end of the day.
>
> OK this is now done. We have a new git tree which John maintains for
> the database:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git

Oh and this has a tag for date on the release so we'd get a new
wireless-regdb package for each new tag.

  Luis

Re: crda packaging

[Davide Pesavento]

On Mon, Nov 17, 2008 at 23:21, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> On Mon, Nov 17, 2008 at 12:27 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
>> On Sun, Nov 16, 2008 at 12:58:43PM -0800, Davide Pesavento wrote:
>>> On Mon, Oct 20, 2008 at 02:28, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>>> > On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
>>> >>
>>> >> Do you think the regulatory database should be split from the package
>>> >> that contains the crda daemon? If so, regulatory.bin should be
>>> >> versioned as well...
>>> >
>>> > Yes, absolutely, the idea is to split db.txt into a separate git tree
>>> > too actually so that should help with keeping track of changes
>>> > separately and thinking of them separately.
>>> >
>>> > 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.
>>> >
>>> >  Luis
>>> >
>>>
>>> Any updates on this?
>>
>> I think we'll have this done by the end of the day.
>
> OK this is now done. We have a new git tree which John maintains for
> the database:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git
>
> All you need from that is the regulatory.bin, you don't need to run
> make or anything, just cp the regulatory.bin to the preferred
> location. Right now this is built into CRDA and its
> /usr/lib/crda/regulatory.bin.
>
> Then do a git pull on crda and try to build and let us know if you run
> into any issues for packaging. The documentation on the
> wireless.kernel.org wiki needs some good updating.
>
>  Luis
>

Great! Thanks a lot!
Are there any tarballs around? I couldn't find them on
http://wireless.kernel.org/download/...

Regards,
Davide

Re: crda packaging

[Luis R. Rodriguez]

On Sun, Nov 23, 2008 at 10:40:58AM -0800, Davide Pesavento wrote:
> On Mon, Nov 17, 2008 at 23:21, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> > On Mon, Nov 17, 2008 at 12:27 PM, Luis R. Rodriguez
> > <lrodriguez@atheros.com> wrote:
> >> On Sun, Nov 16, 2008 at 12:58:43PM -0800, Davide Pesavento wrote:
> >>> On Mon, Oct 20, 2008 at 02:28, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> >>> > On Sun, Oct 19, 2008 at 8:57 AM, Davide Pesavento <davidepesa@gmail.com> wrote:
> >>> >>
> >>> >> Do you think the regulatory database should be split from the package
> >>> >> that contains the crda daemon? If so, regulatory.bin should be
> >>> >> versioned as well...
> >>> >
> >>> > Yes, absolutely, the idea is to split db.txt into a separate git tree
> >>> > too actually so that should help with keeping track of changes
> >>> > separately and thinking of them separately.
> >>> >
> >>> > 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.
> >>> >
> >>> >  Luis
> >>> >
> >>>
> >>> Any updates on this?
> >>
> >> I think we'll have this done by the end of the day.
> >
> > OK this is now done. We have a new git tree which John maintains for
> > the database:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-regdb.git
> >
> > All you need from that is the regulatory.bin, you don't need to run
> > make or anything, just cp the regulatory.bin to the preferred
> > location. Right now this is built into CRDA and its
> > /usr/lib/crda/regulatory.bin.
> >
> > Then do a git pull on crda and try to build and let us know if you run
> > into any issues for packaging. The documentation on the
> > wireless.kernel.org wiki needs some good updating.
> >
> >  Luis
> >
> 
> Great! Thanks a lot!
> Are there any tarballs around? I couldn't find them on
> http://wireless.kernel.org/download/...

I was working on that and now I'm done, heh. I'll send a new post
announcing these URLs.

  Luis