From: Hugh Dickins <hughd@google.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cfg80211: stop demanding lots of new stuff
Date: Thu, 18 Jan 2018 13:11:22 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.1801181309530.15660@eggly.anvils> (raw)
In-Reply-To: <alpine.LSU.2.11.1801181242280.14771@eggly.anvils>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2298 bytes --]
A familiar error, let's try to attach this time...
On Thu, 18 Jan 2018, Hugh Dickins wrote:
> On Thu, 18 Jan 2018, Johannes Berg wrote:
> > On Wed, 2018-01-17 at 14:55 -0800, Hugh Dickins wrote:
> > > "make oldconfig" from 4.14 (when CONFIG_CFG80211_CERTIFICATION_ONUS
> > > is not set) to 4.15-rc, gets into asking lots of new questions, and
> > > configuring in unwanted stuff: I'm unsure of my Kconfig skills, but
> > > it looks like CFG80211_REQUIRE_SIGNED_REGDB's "default y" needs to
> > > be toned down when we don't even have CFG80211_CERTIFICATION_ONUS.
> >
> > No, this is wrong - we want default configurations to be able to load a
> > signed regulatory database and validate the signature.
>
> Great to enable that, but not so great to force new stuff on everyone.
> It doesn't surprise me at all if the patch here is the wrong one,
> but something needs to be done differently in this configuration.
>
> Perhaps you did not try on a system without SYSTEM_DATA_VERIFICATION
> already enabled - that "select SYSTEM_DATA_VERIFICATION" seems to be
> taking effect even when CFG80211_REQUIRE_SIGNED_REGDB is not enabled,
> and pulls in a boatload. I agree that seems strange: perhaps the
> Kconfig problem is somewhere else entirely.
>
> Attached my old 4.14 config, so you can see for yourself - thanks.
>
> In fact, I cannot even build the resulting config, without scurrying
> around to update userspace with stuff I never needed before:
>
> HOSTCC scripts/extract-cert
> scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file or directory
>
> Hugh
>
> >
> > johannes
> >
> > >
> > > Signed-off-by: Hugh Dickins <hughd@google.com>
> > > ---
> > >
> > > net/wireless/Kconfig | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > --- 4.15-rc8/net/wireless/Kconfig 2017-12-03 10:22:51.928845056 -0800
> > > +++ linux/net/wireless/Kconfig 2018-01-14 19:20:22.595472965 -0800
> > > @@ -89,7 +89,7 @@ config CFG80211_CERTIFICATION_ONUS
> > >
> > > config CFG80211_REQUIRE_SIGNED_REGDB
> > > bool "require regdb signature" if CFG80211_CERTIFICATION_ONUS
> > > - default y
> > > + default CFG80211_CERTIFICATION_ONUS
> > > select SYSTEM_DATA_VERIFICATION
> > > help
> > > Require that in addition to the "regulatory.db" file a
[-- Attachment #2: Type: APPLICATION/x-gzip, Size: 19891 bytes --]
next prev parent reply other threads:[~2018-01-18 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 22:55 [PATCH] cfg80211: stop demanding lots of new stuff Hugh Dickins
2018-01-18 6:47 ` Johannes Berg
2018-01-18 21:07 ` Hugh Dickins
2018-01-18 21:09 ` Randy Dunlap
2018-01-18 21:11 ` Hugh Dickins [this message]
2018-01-18 21:20 ` Johannes Berg
2018-02-03 16:28 ` Kevin Groeneveld
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=alpine.LSU.2.11.1801181309530.15660@eggly.anvils \
--to=hughd@google.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--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).