docs(SECURITY): Shift vulnerability reporting directly to GitHub

This patch adjust the to follow a new workflow, which
results in reports ending up on GitHub without going through my mailbox,
this frees resources on my side as well as reducing the bus factor.

Since most of the time, I do an editorial copy of the content of the
E-Mail into GitHub's vulnerability template, this should help to reduce
manual processes.

Signed-off-by: Sheogorath <>
This commit is contained in:
Sheogorath 2023-01-23 21:28:43 +01:00 committed by Philip Molares
parent 3bae6d9637
commit 58819f6018

View file

@ -13,12 +13,17 @@ ressources to maintain multiple versions.
## Reporting a Vulnerability
If you find a vulnerability for [this repository][repo], please report it to
Please go to ["Issues" > "New" > "Report a security vulnerability"][report]. This
allows you to get in direct, but private contact with us. There is some more detailed
documentation [available by GitHub][github_report_docs].
Please report your findings OpenPGP encrypted. If you are not aware of
how to use OpenPGP, please refer to [@SISheogorath's OpenPGP page][openpgp],
which will take care of the encryption for you.
> **Tip**: In this form, only the title and description are mandatory [so don't
> worry if you can't fill everything]. […] However, we recommend security
> researchers provide as much information as possible on the form so that [we]
> can make an informed decision about the submitted report. You can adopt the
> template used by [GitHub's] security researchers from the GitHub Security
> Lab, which is available on the [github/securitylab
> repository][best_practice]."
We'll get back to you as soon as possible. You can expect an answer within
3 days, in rare cases within a month. If you don't get a reply within a month,
@ -37,7 +42,8 @@ like and allow people to make an informed decision about using HedgeDoc.
If you have any further questions, feel free to reach out to the
[community chat][community_chat] or the mentioned contacts above.