From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>,
Kel Modderman <kel@otaku42.de>,
Kel Modderman <kelmo@kanotixguide.org>
Subject: Re: [ANN] crda: v1.1.1
Date: Tue, 26 Jan 2010 10:59:04 -0800 [thread overview]
Message-ID: <43e72e891001261059t7a9d8fcdn1bdc7691d3e9d7be@mail.gmail.com> (raw)
In-Reply-To: <E1NZoGF-0008Cr-CL@sipsolutions.net>
On Tue, Jan 26, 2010 at 8:27 AM, <wireless@sipsolutions.net> wrote:
>
> A new release of crda (v1.1.1) is available at:
>
> http://wireless.kernel.org/download/crda/crda-1.1.1.tar.bz2
>
> SHA1 sum: 73643b3f49b34c4150df4abb793a36792cc68fb7
>
> Here is the short log of the changes included in this
> release:
>
> Luis R. Rodriguez (1):
> Space fix
>
> Paul Fertser (1):
> Implement runtime loading of RSA public keys
Thanks to Paul Ferster for this patch. Its worth elaborating a little
more on this.
Typically CRDA has only allowed adding of public keys at build time.
Adding alternative public keys for CRDA allows for third party
authored files to be redistributed and used. This is now documented
here:
http://wireless.kernel.org/en/developers/Regulatory#Custom_regulatory_information
With the new patch by Paul you can read keys put in place on a
preconfigured directory, by default /etc/wireless-regdb/pubkeys. This
is currently only available with USE_OPENSSL=1 as gcrypt lacks a PEM
parser.
> Pavel Roskin (1):
> CRDA and cross-compilation
>
> Tim Gardner (1):
> crda: Cosmetic fix for udev path
>
Luis
prev parent reply other threads:[~2010-01-26 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 16:27 [ANN] crda: v1.1.1 wireless
2010-01-26 18:59 ` Luis R. Rodriguez [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=43e72e891001261059t7a9d8fcdn1bdc7691d3e9d7be@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=kel@otaku42.de \
--cc=kelmo@kanotixguide.org \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-wireless@vger.kernel.org \
/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