From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 00/11] Documentation: define a barebox threat model
Date: Tue, 29 Sep 2026 09:42:24 +0200 [thread overview]
Message-ID: <179066774422.746017.3999649954446570551.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20260928112731.1271094-1-a.fatoum@pengutronix.de>
On Mon, 28 Sep 2026 13:26:55 +0200, Ahmad Fatoum wrote:
> The security considerations chapter is written for integrators and
> tells them what to configure.
>
> Security researchers may not know how barebox is integrated, so let's
> document what we count as a security vulnerability and what's a normal
> bug.
>
> [...]
Applied, thanks!
[01/11] Documentation: security: unnest hardening sections from dm-verity section
https://git.pengutronix.de/cgit/barebox/commit/?id=c0cdd23b4c61 (link may not be stable)
[02/11] Documentation: security: clarify development key insecurity
https://git.pengutronix.de/cgit/barebox/commit/?id=8dc76a8df393 (link may not be stable)
[03/11] Documentation: security: require signature verification to be pinned
https://git.pengutronix.de/cgit/barebox/commit/?id=2ed2d9dc91fc (link may not be stable)
[04/11] Documentation: security: document trust for builtin devicetree
https://git.pengutronix.de/cgit/barebox/commit/?id=19aa2d73e335 (link may not be stable)
[05/11] Documentation: security: clarify the environment section
https://git.pengutronix.de/cgit/barebox/commit/?id=6f05b3974006 (link may not be stable)
[06/11] Documentation: security: describe shell and environment as trust boundary
https://git.pengutronix.de/cgit/barebox/commit/?id=e3cf9dcf37a1 (link may not be stable)
[07/11] Documentation: security: document the barebox update attack surface
https://git.pengutronix.de/cgit/barebox/commit/?id=e970228de462 (link may not be stable)
[08/11] Documentation: security: update for barebox dm-verity support
https://git.pengutronix.de/cgit/barebox/commit/?id=cdc811322e49 (link may not be stable)
[09/11] Documentation: security: add anchors for the different sections
https://git.pengutronix.de/cgit/barebox/commit/?id=e6c151d4b3e8 (link may not be stable)
[10/11] Documentation: define a barebox threat model
https://git.pengutronix.de/cgit/barebox/commit/?id=482b9b909058 (link may not be stable)
[11/11] README, SECURITY.md: link the threat model and security considerations
https://git.pengutronix.de/cgit/barebox/commit/?id=6c54a2974517 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2026-09-29 7:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 11:26 Ahmad Fatoum
2026-09-28 11:26 ` [PATCH 01/11] Documentation: security: unnest hardening sections from dm-verity section Ahmad Fatoum
2026-09-28 11:26 ` [PATCH 02/11] Documentation: security: clarify development key insecurity Ahmad Fatoum
2026-09-28 11:26 ` [PATCH 03/11] Documentation: security: require signature verification to be pinned Ahmad Fatoum
2026-09-28 11:26 ` [PATCH 04/11] Documentation: security: document trust for builtin devicetree Ahmad Fatoum
2026-09-28 11:27 ` [PATCH 05/11] Documentation: security: clarify the environment section Ahmad Fatoum
2026-09-28 11:27 ` [PATCH 06/11] Documentation: security: describe shell and environment as trust boundary Ahmad Fatoum
2026-09-28 11:27 ` [PATCH 07/11] Documentation: security: document the barebox update attack surface Ahmad Fatoum
2026-09-28 11:27 ` [PATCH 08/11] Documentation: security: update for barebox dm-verity support Ahmad Fatoum
2026-09-28 11:27 ` [PATCH 09/11] Documentation: security: add anchors for the different sections Ahmad Fatoum
2026-09-28 11:27 ` [PATCH 10/11] Documentation: define a barebox threat model Ahmad Fatoum
2026-09-28 11:27 ` [PATCH 11/11] README, SECURITY.md: link the threat model and security considerations Ahmad Fatoum
2026-09-29 7:42 ` 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=179066774422.746017.3999649954446570551.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@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