mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] Documentation: security: add cross references with SECURITY.md
Date: Tue,  6 May 2025 13:24:49 +0200	[thread overview]
Message-ID: <20250506112449.1100020-1-a.fatoum@pengutronix.de> (raw)

We have a top-level SECURITY.md, because it's handled specially by the
Github Web UI. Additionally, we have a security chapter in the
documentation, so add references between the two for easier
discoverability.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/user/security.rst | 7 +++++++
 SECURITY.md                     | 5 +++++
 2 files changed, 12 insertions(+)

diff --git a/Documentation/user/security.rst b/Documentation/user/security.rst
index 5beedfc9a5bf..cc15c8b512b2 100644
--- a/Documentation/user/security.rst
+++ b/Documentation/user/security.rst
@@ -170,3 +170,10 @@ a compiled-in RSA public key. Board code should read the JSON Web Token
 (e.g., from a raw partition on a USB mass storage device), verify the
 serial number claim within against the board's actual serial number and only
 then unlock any debugging functionality.
+
+Security Policy
+---------------
+
+For general information on supported versions and how to report security
+vulnerabilities, refer to the top-level
+`SECURITY.md <https://github.com/barebox/barebox/security/policy>`_ document.
diff --git a/SECURITY.md b/SECURITY.md
index 476ab3186e04..9dd19d73d0aa 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -12,3 +12,8 @@ Compatibility with old kernels is maintained over barebox releases.
 
 Please report security vulnerabilities to security@barebox.org.
 We will work with the reporter to create a fix and to coordinate the disclosure.
+
+## Securing barebox
+
+Refer to the [Security Considerations](https://www.barebox.org/doc/latest/user/security.html)
+chapter of the documentation for information on how to configure barebox securely.
-- 
2.39.5




             reply	other threads:[~2025-05-06 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 11:24 Ahmad Fatoum [this message]
2025-05-08  7:34 ` Sascha Hauer

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=20250506112449.1100020-1-a.fatoum@pengutronix.de \
    --to=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