]> git.kaiwu.me - haproxy.git/commit
projects / haproxy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d8c2cb4) | patch
DOC: security: clarify how to send proper reports
authorWilly Tarreau <w@1wt.eu>
Thu, 12 Nov 2026 15:37:55 +0000 (16:37 +0100)
committerWilly Tarreau <w@1wt.eu>
Thu, 12 Nov 2026 17:12:23 +0000 (18:12 +0100)
commit2f9476dc46fda926b032313f33a41887b3738625
tree657a7bbac5e0178c7063be57efd82f5107068173tree | snapshot
parentd8c2cb4bf64104b0fecf155ff4ff14e334a4e010commit | diff
DOC: security: clarify how to send proper reports

Due to the advent of AI, reports are becoming extremely common the the
security list and seem to be competing in a race to bad quality, wasting
everyone's time and nerves. So let's clarify a few points on the expected
format and expected behavior.

Also let's fix 2 lines that were ruined by the create-release script.
doc/security.txt diff | blob | history
haproxy upstream