From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Krishna Chaitanya <chaitanya.mgit@gmail.com>,
"wireless-regdb@lists.infradead.org"
<wireless-regdb@lists.infradead.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: CRDA: Build Fail: Database signature verification failed
Date: Fri, 24 Jan 2014 19:01:13 -0500 [thread overview]
Message-ID: <20140125000113.GO4309@tuxdriver.com> (raw)
In-Reply-To: <CAB=NE6U7zy8MeO4qLuWsEC_t69JKkS2=98crGrp4073=5WHU9Q@mail.gmail.com>
On Fri, Jan 24, 2014 at 03:02:11PM -0800, Luis R. Rodriguez wrote:
> On Mon, Dec 16, 2013 at 11:14 PM, Krishna Chaitanya
> <chaitanya.mgit@gmail.com> wrote:
> > On Tue, Dec 17, 2013 at 12:20 PM, Krishna Chaitanya
> > <chaitanya.mgit@gmail.com> wrote:
> >> Hi,
> >>
> >> With the latest git source, i am seeing a build failure with the below error.
> >>
> >> LD crda
> >> CC intersect.o
> >> LD intersect
> >> CC regdbdump.o
> >> LD regdbdump
> >> CC db2rd.o
> >> LD db2rd
> >> CC optimize.o
> >> LD optimize
> >> CHK /usr/lib/crda/regulatory.bin
> >> Database signature verification failed.
> >> Invalid or empty regulatory file, note: a binary regulatory file should be used.
> >> make: *** [verify] Error 234
> >>
> >> Is there something wrong with the certificate?
> >>
> > Additional info:
> >
> > # regdbdump /usr/lib/crda/regulatory.bin
> > Database signature verification failed.
> > # ls -l /usr/lib/crda/regulatory.bin
> > -rw-r--r-- 1 root root 3344 Dec 16 17:34 /usr/lib/crda/regulatory.bin
> >
> > regualtory.bin copied from wireless-regdb latest git.
>
> John, what ever happened with this, I forget.
I thought these issues were resolved...?
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-01-25 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 6:50 CRDA: Build Fail: Database signature verification failed Krishna Chaitanya
2013-12-17 7:14 ` Krishna Chaitanya
2014-01-24 23:02 ` Luis R. Rodriguez
2014-01-25 0:01 ` John W. Linville [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=20140125000113.GO4309@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=chaitanya.mgit@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=wireless-regdb@lists.infradead.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).