Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kazuhiko Shiozaki
gitlab-ce
Commits
33eae334
Commit
33eae334
authored
Nov 19, 2013
by
Dmitriy Zaporozhets
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'full-post-to-oss-security' of /home/git/repositories/gitlab/gitlabhq
parents
6cc3cc51
6413bfb5
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/release/security.md
doc/release/security.md
+2
-2
No files found.
doc/release/security.md
View file @
33eae334
...
...
@@ -26,10 +26,10 @@ Please report suspected security vulnerabilities in private to support@gitlab.co
1.
Send out an email to the subscribers mailing list on MailChimp
1.
Send out an email to
[
the community google mailing list
](
https://groups.google.com/forum/#!forum/gitlabhq
)
1.
Send out an email to
[
the GitLab newsletter list
](
http://gitlab.us5.list-manage.com/subscribe?u=498dccd07cf3e9482bee33ba4&id=98a9a4992c
)
1.
Post a signed copy of our announcement to
[
oss-security
](
http://www.openwall.com/lists/oss-security/
)
and request a CVE number
1.
Post a signed copy of our
complete
announcement to
[
oss-security
](
http://www.openwall.com/lists/oss-security/
)
and request a CVE number
1.
Add the security researcher to the
[
Security Researcher Acknowledgments list
](
http://www.gitlab.com/vulnerability-acknowledgements/
)
1.
Thank the security researcher in an email for their cooperation
1.
Update the blogpost
s
when we receive the CVE number
1.
Update the blogpost
and the CHANGELOG
when we receive the CVE number
The timing of the code merge into master should be coordinated in advance.
After the merge we strive to publish the announcements within 60 minutes.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment