From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 3/3] environment: add explicit option to allow searching for environment devices
Date: Tue, 28 Apr 2026 11:24:12 +0200 [thread overview]
Message-ID: <20260428-env-autoprobe-v1-3-9cdedfa0752e@pengutronix.de> (raw)
In-Reply-To: <20260428-env-autoprobe-v1-0-9cdedfa0752e@pengutronix.de>
Add an explicit Kconfig option to allow searching the environment storage path
based on the barebox environment partition GUID.
So far this depended on CONFIG_INSECURE being set. First of all loading the
barebox environment from storage is always insecure as the barebox environment
doesn't have any security measures. The difference that comes with loading
the environment from an explicitly specified storage device and autoprobing
it from the available block devices is that with the former an attacker would
need access to the internal storage whereas with the latter barebox could
be tricked into loading an environment from an external SD card.
Whether or not this is acceptable depends on the case, so ask the user for it.
Real security can only be provided by not loading an environment from storage
at all, but that can be controlled at compile time by disabling CONFIG_ENV_HANDLING
or at runtime by security policies.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
common/Kconfig | 14 ++++++++++++++
common/environment.c | 2 +-
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/common/Kconfig b/common/Kconfig
index fd422714d5..f74f06b4ad 100644
--- a/common/Kconfig
+++ b/common/Kconfig
@@ -987,6 +987,20 @@ config ENV_HANDLING
A safe use of the mutable environment may be possible if board code only
mounts it after verifying a JSON Web Token that enables a debug mode.
+config ENV_HANDLING_AUTOPROBE
+ depends on ENV_HANDLING
+ bool "Autoprobe for environment devices"
+ default y
+ help
+ There are two ways for specifying where the barebox environment is. The first one
+ specifies the path explicitly in the device tree or board code. The other one is
+ to automatically search it on block devices which is enabled with this option.
+ Here a partition with the barebox environment GUID is searched. If this option
+ is enabled and no environment is chosen by device tree or board code then a block
+ device containing a partition with the barebox environment GUID is used for the
+ environment. A block device barebox has booted from is preferred over other block
+ devices.
+
config DEFAULT_ENVIRONMENT
select CRC32
bool
diff --git a/common/environment.c b/common/environment.c
index f883a520c6..a3281feca2 100644
--- a/common/environment.c
+++ b/common/environment.c
@@ -53,7 +53,7 @@ struct action_data {
#define TMPDIR "/.defaultenv"
-static int global_env_autoprobe = IS_ENABLED(CONFIG_INSECURE);
+static int global_env_autoprobe = IS_ENABLED(CONFIG_ENV_HANDLING_AUTOPROBE);
static char *default_environment_path;
void default_environment_path_set(const char *path)
--
2.47.3
prev parent reply other threads:[~2026-04-28 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 9:24 [PATCH 0/3] environment: Allow autoprobing env devices without CONFIG_INSECURE Sascha Hauer
2026-04-28 9:24 ` [PATCH 1/3] environment: Drop /dev/env0 default Sascha Hauer
2026-04-28 9:24 ` [PATCH 2/3] environment: add global.env.path Sascha Hauer
2026-04-28 9:24 ` Sascha Hauer [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=20260428-env-autoprobe-v1-3-9cdedfa0752e@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@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