2
0
Эх сурвалжийг харах

chore: update security advisory reporting process

[skip ci]
ᴊᴏᴇ ᴄʜᴇɴ 1 долоо хоног өмнө
parent
commit
5e7c599755
1 өөрчлөгдсөн 6 нэмэгдсэн , 4 устгасан
  1. 6 4
      SECURITY.md

+ 6 - 4
SECURITY.md

@@ -12,13 +12,15 @@ Existing vulnerability reports are being tracked in [GitHub Security Advisories]
 > Starting **Nov 9, 2023 00:00 UTC**, only security vulnerabilities reported through [GitHub Security Advisories](https://github.com/gogs/gogs/security/advisories/new) are accepted.
 > Pre-existing vulnerability reported through https://huntr.dev/ or email (`security@gogs.io`) will continue to be worked through.
 
-1. Report an advisory for the vulnerability
-1. Project maintainers review the advisory and either:
+1. Report an advisory for the vulnerability.
+    - Please be aware that **only advisories reported in plain English** will be reviewed.
+1. Project maintainers review the advisory:
     - Ask clarifying questions
+    - Make sure there was no prior advisory exists for the same vulnerability
     - Confirm or deny the vulnerability
-1. Once the vulnerability is confirmed, the reporter may submit a patch or wait for project maintainers to patch.
+1. Once the advisory is accepted, the reporter may submit a patch or wait for project maintainers to patch.
     - The latter is usually significantly slower.
 1. Patch releases will be made for the supported versions.
 1. After 14 days of the release, publish the corresponding advisory on [GitHub Security Advisories](https://github.com/gogs/gogs/security/advisories).
 
-Thank you!
+Thank you for making open source community a better place!