From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Fabian Pflug <f.pflug@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH] security: policy: allow querying the active policy
Date: Tue, 11 Nov 2025 09:59:21 +0100 [thread overview]
Message-ID: <98968c9c-4edf-46d3-a317-01fb79b925f4@pengutronix.de> (raw)
In-Reply-To: <20251110214648.2738052-1-f.pflug@pengutronix.de>
Hello Fabian,
On 11/10/25 10:46 PM, Fabian Pflug wrote:
> Sometimes it is needed from board code to not to check what is allowed,
> but what is the currently activated security policy to do some stuff.
As you know, security policies were a recent addition in the last
month's release and we are still gathering experience with how to best
use it.
May I ask what you are using the name for? I envisioned the name to be
just a descriptive string and that boards would define their own
SCONFIG_ symbols if they need to control something.
Thanks,
Ahmad
>
> Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
> ---
> include/security/policy.h | 1 +
> security/policy.c | 8 ++++++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/include/security/policy.h b/include/security/policy.h
> index c41220ef3b..3eedf6e5ac 100644
> --- a/include/security/policy.h
> +++ b/include/security/policy.h
> @@ -32,6 +32,7 @@ const struct security_policy *security_policy_get(const char *name);
> int security_policy_activate(const struct security_policy *policy);
> int security_policy_select(const char *name);
> void security_policy_list(void);
> +bool security_policy_is_active(const char *name);
>
> #ifdef CONFIG_SECURITY_POLICY
> int __security_policy_register(const struct security_policy policy[]);
> diff --git a/security/policy.c b/security/policy.c
> index 85333d9e6f..abb956014d 100644
> --- a/security/policy.c
> +++ b/security/policy.c
> @@ -225,6 +225,14 @@ static int security_policy_get_name(struct param_d *param, void *priv)
> return 0;
> }
>
> +bool security_policy_is_active(const char *name)
> +{
> + if (!active_policy)
> + return false;
> +
> + return !strcmp(name, active_policy->name);
> +}
> +
> static int security_init(void)
> {
> register_device(&security_device);
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-11-11 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 21:46 Fabian Pflug
2025-11-11 8:59 ` Ahmad Fatoum [this message]
2025-11-11 10:48 ` Ahmad Fatoum
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=98968c9c-4edf-46d3-a317-01fb79b925f4@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pflug@pengutronix.de \
/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