[PATCH RFC 07/17] security: policy: support externally provided configs

[Ahmad Fatoum]

On 8/14/25 15:06, Ahmad Fatoum wrote:
> From: Ahmad Fatoum <a.fatoum at barebox.org>
> +	help
> +	  Space separated list of security policies that should be
> +	  compiled into barebox and registered. This option currently
> +	  requires security policies to have the .sconfig extension
> +	  and be located in the barebox source tree's security/
> +	  directory.
> +	  If left empty, only security policies explicitly provided
> +	  and registered by board code will be available.

With an eye towards removing this limitation in future, once the build
system is adapted, I would change this in v2 to require a security/
prefix in front of the configs now. Then at some point in the future, we
could allow arbitrary paths without changing semantics for existing users.

-- 
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 |