Add a section on reporting security vulnerabilities #89
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…to the security page. The information about requesting a CVE is taken from https://cve.mitre.org/cve/request_id.html It seems much less clear how to tell the world about your issue and with no well recognised route, as far as I can tell. In the absence of any well trodden route I have suggested the ruby-talk mailing list since people already use this to announce new versions of gems. Further discussion can be found in issue rubygems#62
| first step should be to check whether this is a known vulnerability. | ||
|
|
||
| If this looks like a newly discovered vulnerability then you should | ||
| content the author(s) privately (i.e. not via a pull request or issue on public |
There was a problem hiding this comment.
Thanks. Fixed in 4737de2
|
Looks good to me, any thoughts from rubysec? rubysec/rubysec.github.io#7 |
drbrain
added a commit
that referenced
this pull request
Jul 14, 2014
…lnerabilities Add a section on reporting security vulnerabilities
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…to the security page.
The information about requesting a CVE is taken from
https://cve.mitre.org/cve/request_id.html
It seems much less clear how to tell the world about your
issue and with no well recognised route, as far as I can tell.
In the absence of any well trodden route I have suggested the
ruby-talk mailing list since some people already use this to
announce new versions of gems.
Further discussion can be found in issue #62