From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 79918b: SECURITY: Add top-level security doc
Date: Fri, 28 Aug 2026 14:29:59 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/49592c-e81413@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 79918b87dccdb804c1fe338fe8fdfcb77a0e8293
https://github.com/bluez/bluez/commit/79918b87dccdb804c1fe338fe8fdfcb77a0e8293
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-28 (Fri, 28 Aug 2026)
Changed paths:
M Makefile.am
M README
A SECURITY.md
Log Message:
-----------
SECURITY: Add top-level security doc
This will replace the existing documentation written 5 years ago to take
into account the new tools and the new rules around dealing with
security issues.
The new workflow replaces email-based reporting with the GitHub security
advisory tools, explains the CVE ID assignment process, and places strict
limits on the amount of work that can be demanded from BlueZ developers.
It is customary in 2026 to have a top-level SECURITY.md file which
explains the vulnerability workflow.
Commit: e8141342284be2a52e16565b96b513ebe1297d84
https://github.com/bluez/bluez/commit/e8141342284be2a52e16565b96b513ebe1297d84
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-28 (Fri, 28 Aug 2026)
Changed paths:
R doc/security-bugs.rst
Log Message:
-----------
doc: Remove obsolete security-bugs.rst
Compare: https://github.com/bluez/bluez/compare/49592cbc1416...e8141342284b
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-28 21:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/master/49592c-e81413@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.