From: "John W. Linville" <linville@tuxdriver.com>
To: "Thomas Bächler" <thomas@archlinux.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [ANN] wireless-regdb: master-2010-11-22
Date: Wed, 24 Nov 2010 12:06:40 -0500 [thread overview]
Message-ID: <20101124170639.GD7435@tuxdriver.com> (raw)
In-Reply-To: <4CED4464.2000106@archlinux.org>
On Wed, Nov 24, 2010 at 05:59:16PM +0100, Thomas Bächler wrote:
> Am 23.11.2010 05:10, schrieb
> wireless-cdvu00un1VgdHxzADdlk8Q@public.gmane.org:
> > A new release of wireless-regdb (master-2010-11-22) is available at:
> >
> > http://wireless.kernel.org/download/wireless-regdb/wireless-regdb-2010.11.22.tar.bz2
> >
> > SHA1 sum: d0b008b4d32105cf6a87860b5a69e8066b03baaa
> >
> >
> > For your convenience the individual regulatory.bin file can be downloaded from:
> >
> > http://wireless.kernel.org/download/wireless-regdb/regulatory.bins/2010.11.22-regulatory.bin
> >
> > SHA1 sum d7e558216ebe4d5ad01ccb0029c64456f740b9fd
>
> Hello,
>
> the binary does not work for me:
>
> $ sha1sum 2010.11.22-regulatory.bin
> d7e558216ebe4d5ad01ccb0029c64456f740b9fd 2010.11.22-regulatory.bin
> $ regdbdump ./2010.11.22-regulatory.bin
> Database signature verification failed.
>
> The old 2009.11.25-regulatory.bin works fine.
It seems to be working for me, even on a freshly installed RHEL6 box
(so no random keys scattered about).
Anyone else seeing this issue? I seem to remember that we had a
similar problem some time back...?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-11-24 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 4:10 [ANN] wireless-regdb: master-2010-11-22 wireless
2010-11-24 16:59 ` Thomas Bächler
2010-11-24 17:06 ` John W. Linville [this message]
2010-11-24 17:33 ` Luis R. Rodriguez
2010-11-24 17:50 ` John W. Linville
2010-11-24 18:04 ` Luis R. Rodriguez
2010-11-24 18:50 ` John W. Linville
2010-11-24 19:06 ` Luis R. Rodriguez
2010-11-25 13:59 ` Thomas Bächler
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=20101124170639.GD7435@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas@archlinux.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;
as well as URLs for NNTP newsgroup(s).