Return-path: Received: from venema.h4ckr.net ([217.24.1.135]:55101 "EHLO venema.h4ckr.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1764189AbZCYRpe (ORCPT ); Wed, 25 Mar 2009 13:45:34 -0400 From: Kel Modderman To: debian-devel@lists.debian.org Subject: Re: [renamed] Debian crda? Date: Thu, 26 Mar 2009 03:45:30 +1000 Cc: "linux-wireless@vger.kernel.org" , "Luis R. Rodriguez" References: <43e72e890903250009hbe7bcfal546dddf731820b8e@mail.gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-Id: <200903260345.30678.kel@otaku42.de> (sfid-20090325_184538_257439_0C00726D) Sender: linux-wireless-owner@vger.kernel.org List-ID: 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] 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. Thanks, Kel.