瀏覽代碼

Merge pull request #1873 from PrivateBin/docs/security

docs: favour GitHub security form over mail
El RIDO 4 周之前
父節點
當前提交
8238a1492a
共有 1 個文件被更改,包括 6 次插入4 次删除
  1. 6 4
      SECURITY.md

+ 6 - 4
SECURITY.md

@@ -9,13 +9,15 @@
 
 
 ## Reporting a Vulnerability
 ## Reporting a Vulnerability
 
 
-You can send us email at security@privatebin.org. You should be able to get
+We suggest to [use the corresponding GitHub form](https://github.com/PrivateBin/PrivateBin/security/advisories/new)
+to report a new vulnerability directly on GitHub. [It can be handled there](https://docs.github.com/code-security/how-tos/report-and-fix-vulnerabilities/report-privately)
+and all necessary steps like verifying the vulnerability, crediting the finder
+and drafting a security advisory will be done there.
+
+You can also send us email at security@privatebin.org. You should be able to get
 a response within a week (usually during the next weekend). The respondee will
 a response within a week (usually during the next weekend). The respondee will
 reply from their personal address and can offer you their GPG public key to
 reply from their personal address and can offer you their GPG public key to
 support end-to-end encrypted communication on sensitive topics or attachments.
 support end-to-end encrypted communication on sensitive topics or attachments.
 
 
-You can also [use the corresponding GitHub form](https://github.com/PrivateBin/PrivateBin/security/advisories/new)
-to report a new vulnerability directly on GitHub.
-
 You can also contact us via the regular issue tracker if the risk of early
 You can also contact us via the regular issue tracker if the risk of early
 publication is low or you would request input from other PrivateBin users.
 publication is low or you would request input from other PrivateBin users.