[bluez/bluez] 962b82: SECURITY: Add top-level security doc

[bluez/bluez] 962b82: SECURITY: Add top-level security doc

[hadess]

  Branch: refs/heads/1152091
  Home:   https://github.com/bluez/bluez
  Commit: 962b822924d38541933664c740938f72aba02f86
      https://github.com/bluez/bluez/commit/962b822924d38541933664c740938f72aba02f86
  Author: Bastien Nocera <hadess@hadess.net>
  Date:   2026-08-26 (Wed, 26 Aug 2026)

  Changed paths:
    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: c036545fa7a17b3a3759d2c34b9ec168959b80db
      https://github.com/bluez/bluez/commit/c036545fa7a17b3a3759d2c34b9ec168959b80db
  Author: Bastien Nocera <hadess@hadess.net>
  Date:   2026-08-26 (Wed, 26 Aug 2026)

  Changed paths:
    R doc/security-bugs.rst

  Log Message:
  -----------
  doc: Remove obsolete security-bugs.rst


Compare: https://github.com/bluez/bluez/compare/962b822924d3%5E...c036545fa7a1

To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications