From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Johannes Berg <johannes.berg@intel.com>,
<linux-wireless@vger.kernel.org>
Cc: Eugeniu Rosca <erosca@de.adit-jv.com>,
Eugeniu Rosca <roscaeugeniu@gmail.com>
Subject: Re: [PATCH 4/4] cfg80211: implement regdb signature checking
Date: Wed, 25 Aug 2021 12:46:20 +0200 [thread overview]
Message-ID: <20210825104620.GA3561@lxhi-065> (raw)
In-Reply-To: <20171006135532.29550-5-johannes@sipsolutions.net>
Dear Johannes,
Dear Linux wireless,
On Fr, Okt 06, 2017 at 03:55:32 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Currently CRDA implements the signature checking, and the previous
> commits added the ability to load the whole regulatory database
> into the kernel.
>
> However, we really can't lose the signature checking, so implement
> it in the kernel by loading a detached signature (regulatory.db.p7s)
> and check it against built-in keys.
>
> TODO
> - add Seth's key, obviously
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> net/wireless/Kconfig | 30 +++++++++++
> net/wireless/Makefile | 22 ++++++++
> net/wireless/certs/none.x509 | 0
> net/wireless/reg.c | 121 ++++++++++++++++++++++++++++++++++++++++++-
> net/wireless/reg.h | 8 +++
> 5 files changed, 180 insertions(+), 1 deletion(-)
> create mode 100644 net/wireless/certs/none.x509
>
> diff --git a/net/wireless/Kconfig b/net/wireless/Kconfig
> index f050030055c5..da91bb547db3 100644
> --- a/net/wireless/Kconfig
> +++ b/net/wireless/Kconfig
> @@ -83,6 +83,36 @@ config CFG80211_CERTIFICATION_ONUS
> you are a wireless researcher and are working in a controlled
> and approved environment by your local regulatory agency.
>
> +config CFG80211_REQUIRE_SIGNED_REGDB
> + bool "require regdb signature" if CFG80211_CERTIFICATION_ONUS
> + default y
> + select SYSTEM_DATA_VERIFICATION
Since v4.15 commit 90a53e4432b122 ("cfg80211: implement regdb signature
checking"), CFG80211_REQUIRE_SIGNED_REGDB is enabled unconditionally
and users have no flexibility to disable it when
CFG80211_CERTIFICATION_ONUS is unset (since the visibility of
CFG80211_REQUIRE_SIGNED_REGDB depends on CFG80211_CERTIFICATION_ONUS).
Based on the documentation of CFG80211_CERTIFICATION_ONUS, this option
is supposed to stay disabled most of the times, hence users have to live
with CFG80211_REQUIRE_SIGNED_REGDB=y and SYSTEM_DATA_VERIFICATION=y
enabled in their kernel, which consumes a few tens of KB in the
uncompressed binary Image (particularly on arm64).
A few tens of KB is not much, but on embedded systems it matters.
Can you please confirm Wireless subsystem requires
CFG80211_REQUIRE_SIGNED_REGDB=y and SYSTEM_DATA_VERIFICATION=y
regardless of the status of CFG80211_CERTIFICATION_ONUS ?
Thanks,
Eugeniu
prev parent reply other threads:[~2021-08-25 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 13:55 [PATCH 0/4] cfg80211: in-kernel regulatory database Johannes Berg
2017-10-06 13:55 ` [PATCH 1/4] cfg80211: support loading regulatory database as firmware file Johannes Berg
2017-10-06 13:55 ` [PATCH 2/4] cfg80211: support reloading regulatory database Johannes Berg
2017-10-06 13:55 ` [PATCH 3/4] cfg80211: reg: remove support for built-in regdb Johannes Berg
2017-10-06 13:55 ` [PATCH 4/4] cfg80211: implement regdb signature checking Johannes Berg
2021-08-25 10:46 ` Eugeniu Rosca [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=20210825104620.GA3561@lxhi-065 \
--to=erosca@de.adit-jv.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=roscaeugeniu@gmail.com \
/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