security contact

Most active threads (last 7 days)

Recent patches

Latest 3 postings or standalone patches, newest first. Counts below cover matching patches in netdev touching this subsystem.

• security-bugs doc updates v1 · 9 matching patches

  Entire posting: PENDING · 11 of 14 reviewed Open cover letterLifecycle progress covers the full posting, including patches outside this subsystem and inbox.

  • [PATCH 01/14] docs: security-bugs: reorganize the document without changing its contents 2026-11-09
  • [PATCH 03/14] docs: security-bugs: never publish reproducers of bugs with a security impact 2026-11-09
  • [PATCH 05/14] docs: security-bugs: explain how to send a fix that can be applied 2026-11-09
  • [PATCH 06/14] docs: security-bugs: do not send archives or binary attachments 2026-11-09
  • [PATCH 07/14] docs: security-bugs: first-time reporters must send a single report first 2026-11-09
  • [PATCH 08/14] docs: security-bugs: explain what to do when a report gets no response 2026-11-09
  • [PATCH 09/14] docs: security-bugs: reports left unanswered for 7 days will be dropped 2026-11-09
  • [PATCH 11/14] docs: security-bugs: explain why directly sent reports add extra work 2026-11-09
  • [PATCH 12/14] docs: security-bugs: explain why AI-found bugs are handled publicly 2026-11-09
  2026-11-09 · Willy Tarreau <w@1wt.eu>
• REVIEWED · 1 review, 1 by a maintainer [PATCH 10/14] docs: security-bugs: add a section for maintainers receiving reports 2026-11-09 · Willy Tarreau <w@1wt.eu>
• REVIEWED · 1 review, 1 by a maintainer [PATCH 02/14] docs: security-bugs: clarify when to Cc the security team 2026-11-09 · Willy Tarreau <w@1wt.eu>