From: "John W. Linville" <linville@tuxdriver.com>
To: Kel Modderman <kel@otaku42.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] crda: do not embed crypto data when USE_OPENSSL=1
Date: Thu, 4 Mar 2010 10:31:28 -0500 [thread overview]
Message-ID: <20100304153128.GB2910@tuxdriver.com> (raw)
In-Reply-To: <201003050008.51066.kel@otaku42.de>
On Fri, Mar 05, 2010 at 12:08:50AM +1000, Kel Modderman wrote:
> When USE_OPENSSL=1 do not embed crypto data into binary, use the PUBKEY_DIR
> variable just as it is when USE_GCRYPT=1 and just load certs from PUBKEY_DIR
> for signature verification at runtime. Remove ssl support from
> utils/key2pub.py.
>
> This allows wireless-regdb to be built from source and upgraded independently
> of crda and is _crucial_ for distributions who want to build their own
> regulatory.bin.
I don't understand -- isn't this possible already?
> This change does remove support for alternate runtime pubkey dir
> /etc/wireless-regdb/pubkeys, but wireless-regdb does not currently install
> custom pubkeys to /etc/wireless-regdb/pubkeys, and I couldn't care less
> about that feature atm :)
>
> When verification fails provide information about the PUBKEY_DIR variable.
>
> Fix typo (s/make noverify/make all_noverify/).
>
> Signed-off-by: Kel Modderman <kel@otaku42.de>
So you want to remove this feature simply because you don't use
it yourself? What problem is it causing?
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-03-04 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 14:08 [PATCH] crda: do not embed crypto data when USE_OPENSSL=1 Kel Modderman
2010-03-04 15:31 ` John W. Linville [this message]
2010-03-05 0:27 ` Kel Modderman
2010-03-05 1:37 ` John W. Linville
2010-03-05 1:56 ` Kel Modderman
2010-03-05 2:00 ` Kel Modderman
2010-03-05 4:08 ` John W. Linville
2010-03-05 14:59 ` Kel Modderman
2010-03-08 8:08 ` Johannes Berg
2010-03-21 10:46 ` Kel Modderman
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=20100304153128.GB2910@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=kel@otaku42.de \
--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;
as well as URLs for NNTP newsgroup(s).