Commit 6cdd08965e50110030384491204d223a4730d088

Authored by Sytse Sijbrandij
1 parent c938833b

Full post to OSS security.

Showing 1 changed file with 1 additions and 1 deletions   Show diff stats
doc/release/security.md
@@ -24,7 +24,7 @@ Please report suspected security vulnerabilities in private to support@gitlab.co @@ -24,7 +24,7 @@ Please report suspected security vulnerabilities in private to support@gitlab.co
24 1. Send out an email to the subscribers mailing list on MailChimp 24 1. Send out an email to the subscribers mailing list on MailChimp
25 1. Send out an email to [the community google mailing list](https://groups.google.com/forum/#!forum/gitlabhq) 25 1. Send out an email to [the community google mailing list](https://groups.google.com/forum/#!forum/gitlabhq)
26 1. Send out an email to [the GitLab newsletter list](http://gitlab.us5.list-manage.com/subscribe?u=498dccd07cf3e9482bee33ba4&id=98a9a4992c) 26 1. Send out an email to [the GitLab newsletter list](http://gitlab.us5.list-manage.com/subscribe?u=498dccd07cf3e9482bee33ba4&id=98a9a4992c)
27 -1. Post a signed copy of our announcement to [oss-security](http://www.openwall.com/lists/oss-security/) and request a CVE number 27 +1. Post a signed copy of our complete announcement to [oss-security](http://www.openwall.com/lists/oss-security/) and request a CVE number
28 1. Add the security researcher to the [Security Researcher Acknowledgments list](http://www.gitlab.com/vulnerability-acknowledgements/) 28 1. Add the security researcher to the [Security Researcher Acknowledgments list](http://www.gitlab.com/vulnerability-acknowledgements/)
29 1. Thank the security researcher in an email for their cooperation 29 1. Thank the security researcher in an email for their cooperation
30 1. Update the blogposts when we receive a CVE number 30 1. Update the blogposts when we receive a CVE number