On Mon, May 18, 2009 at 4:42 AM, Kel Modderman wrote:
> (Dropped the CC to linux-wireless as it rejected my other attempt to send
> message claiming it was part HTML/Spam. Apologies if you get two copies.)
Maybe you should send plain text email instead?
> I would rather the build process fail i
Hi Luis, Paul,
On Friday 27 March 2009 14:00:20 Luis R. Rodriguez wrote:
> On Wed, Mar 25, 2009 at 9:59 PM, Paul Wise wrote:
> > On Thu, Mar 26, 2009 at 1:19 PM, Luis R. Rodriguez wrote:
> >
> >>> Brainwave: no need to add a second public key to CRDA itself, the
> >>> wireless-regdb could instal
Hi Luis, Paul,
(Dropped the CC to linux-wireless as it rejected my other attempt to send
message claiming it was part HTML/Spam. Apologies if you get two copies.)
On Friday 27 March 2009 14:00:20 Luis R. Rodriguez wrote:
> On Wed, Mar 25, 2009 at 9:59 PM, Paul Wise wrote:
> > On Thu, Mar 26, 200
On Wed, Mar 25, 2009 at 9:59 PM, Paul Wise wrote:
> On Thu, Mar 26, 2009 at 1:19 PM, Luis R. Rodriguez wrote:
>
>>> Brainwave: no need to add a second public key to CRDA itself, the
>>> wireless-regdb could install the public key corresponding to the
>>> private key it was built with.
>>
>> Can y
On Thu, Mar 26, 2009 at 1:19 PM, Luis R. Rodriguez wrote:
>> Brainwave: no need to add a second public key to CRDA itself, the
>> wireless-regdb could install the public key corresponding to the
>> private key it was built with.
>
> Can you elaborate on what you mean? Do you mean for wireless-reg
On Wed, Mar 25, 2009 at 8:08 PM, Paul Wise wrote:
> On Thu, Mar 26, 2009 at 4:03 AM, Paul Wise wrote:
>
>> When we do, just adding a second public key to the CRDA pubkeys dir
>> and using the corresponding private key (from outside the package)
>> during the build process of wireless-regdb would
On Thu, Mar 26, 2009 at 4:03 AM, Paul Wise wrote:
> When we do, just adding a second public key to the CRDA pubkeys dir
> and using the corresponding private key (from outside the package)
> during the build process of wireless-regdb would be just fine. This
> would mean the maintainer of crda w
On Wed, Mar 25, 2009 at 1:25 PM, Luis R. Rodriguez wrote:
> Actually technically it could be a different person. I maintain crda
> upstream and John maintains wireless-regdb upstream, for example. I
> just need John's pubkey file which is non-binary. CRDA just reads the
> regulatory.bin which wir
On Wed, Mar 25, 2009 at 12:03 PM, Paul Wise wrote:
> On Thu, Mar 26, 2009 at 3:42 AM, Kel Modderman wrote:
>
>> The DFSG seems to suggest that the source code to the regulatory database
>> should be modifiable and the derived work distributed under the same license.
>
> It is my understanding tha
On Thu, 26 Mar 2009, Paul Wise wrote:
> debian-volatile isn't an appropriate place for this because many
> stable users don't use volatile and it is fairly important they are
> kept up to date with this, kinda like the timezone database.
AFAIK, volatile.d.o _is_ the proper way to keep the timezone
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 wrote:
> >
> > > Last time I poked them it seemed it was not easy to figure out how to
> > > deal with, if at all, the optio
On Thu, Mar 26, 2009 at 3:42 AM, Kel Modderman wrote:
> The DFSG seems to suggest that the source code to the regulatory database
> should be modifiable and the derived work distributed under the same license.
It is my understanding that:
Debian probably won't need to build the regdb from sourc
On Thursday 26 March 2009 03:41:30 Luis R. Rodriguez wrote:
> On Wed, Mar 25, 2009 at 10:37 AM, Kel Modderman wrote:
> > On Wednesday 25 March 2009 17:51:41 Luis R. Rodriguez wrote:
> >> On Wed, Mar 25, 2009 at 12:47 AM, Luis R. Rodriguez
> >> wrote:
> >> > On Wed, Mar 25, 2009 at 12:39 AM, Paul
On Thu, 2009-03-26 at 03:37 +1000, Kel Modderman wrote:
> > And as its probably best to coordinate with Ubuntu, they have a
> > wireless-crda package which combines both into one package. Its
> > shipping for Jaunty.
>
> And that's the only way to sanely package it (by combining the two pieces
>
On Wednesday 25 March 2009 17:51:41 Luis R. Rodriguez wrote:
> On Wed, Mar 25, 2009 at 12:47 AM, Luis R. Rodriguez wrote:
> > On Wed, Mar 25, 2009 at 12:39 AM, Paul Wise wrote:
> >> On Wed, Mar 25, 2009 at 4:09 PM, Luis R. Rodriguez
> >> wrote:
> >>
> >>> Last time I poked them it seemed it was
On Wednesday 25 March 2009 17:39:03 Paul Wise wrote:
> On Wed, Mar 25, 2009 at 4:09 PM, Luis R. Rodriguez 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
On Wed, Mar 25, 2009 at 10:37 AM, Kel Modderman wrote:
> On Wednesday 25 March 2009 17:51:41 Luis R. Rodriguez wrote:
>> On Wed, Mar 25, 2009 at 12:47 AM, Luis R. Rodriguez wrote:
>> > On Wed, Mar 25, 2009 at 12:39 AM, Paul Wise wrote:
>> >> On Wed, Mar 25, 2009 at 4:09 PM, Luis R. Rodriguez
>
On Wed, Mar 25, 2009 at 12:47 AM, Luis R. Rodriguez wrote:
> On Wed, Mar 25, 2009 at 12:39 AM, Paul Wise wrote:
>> On Wed, Mar 25, 2009 at 4:09 PM, Luis R. Rodriguez 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 rec
On Wed, Mar 25, 2009 at 12:39 AM, Paul Wise wrote:
> On Wed, Mar 25, 2009 at 4:09 PM, Luis R. Rodriguez 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:
On Wed, Mar 25, 2009 at 4:09 PM, Luis R. Rodriguez 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#RSADigitalSig
On Tue, Mar 24, 2009 at 11:44 PM, Kalle Valo wrote:
> "Luis R. Rodriguez" writes:
>
>> As a lot of you know we have a new regulatory implementation for Linux
>> wireless now [1]. We have kept the old regulatory implementation
>> through a Kconfig option, CONFIG_WIRELESS_OLD_REGULATORY.
>> Distrib
21 matches
Mail list logo
