From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Marco Felsch <m.felsch@pengutronix.de>
Subject: Re: [PATCH v2 1/3] common: introduce CONFIG_HAS_INSECURE_DEFAULTS
Date: Tue, 18 Feb 2025 10:05:27 +0100 [thread overview]
Message-ID: <173986952764.2719121.10220055863778577335.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250217180949.3961860-1-a.fatoum@pengutronix.de>
On Mon, 17 Feb 2025 19:09:47 +0100, Ahmad Fatoum wrote:
> Unlike the functionality controlled by CONFIG_INSECURE, most
> functionality in barebox is not as clear-cut: In secure systems, it's
> better to turn off the option, but with enough care, board code may
> disable the option later on.
>
> To help with securing barebox, let's identify these options that need a
> more thorough look by having them select HAS_INSECURE_DEFAULTS.
>
> [...]
Applied, thanks!
[1/3] common: introduce CONFIG_HAS_INSECURE_DEFAULTS
https://git.pengutronix.de/cgit/barebox/commit/?id=1ceb8fadf957 (link may not be stable)
[2/3] Documentation: user: optee: bring up-to-date
https://git.pengutronix.de/cgit/barebox/commit/?id=1db2bef631dd (link may not be stable)
[3/3] Documentation: user: add security consideration for using barebox
https://git.pengutronix.de/cgit/barebox/commit/?id=9fb315ae4bc5 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-02-18 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 18:09 Ahmad Fatoum
2025-02-17 18:09 ` [PATCH v2 2/3] Documentation: user: optee: bring up-to-date Ahmad Fatoum
2025-02-17 18:09 ` [PATCH v2 3/3] Documentation: user: add security consideration for using barebox Ahmad Fatoum
2025-02-18 9:05 ` 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=173986952764.2719121.10220055863778577335.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@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