security disclosure policy
Open
Nobody has claimed this yet.
content
- Dominant language
- HTML
- Stars
- 944
- Forks
- 673
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 9
Description
ref. http://bugs.ruby-lang.org/issues/5821
In short, I think:
http://www.ruby-lang.org/en/security/
should do more to emulate:
http://jruby.org/security
Namely, we don't have a "Disclosure Procedure" section:
> Disclosure Procedure
>
> The JRuby team will endeavor to follow these steps when handling reported vulnerabilities:
>
> 1. Work with the reporter to determine the appropriate fix within 24-72 hours of the initial email report.
> 2. Once the fix has been found, wait for an embargo period of 48 hours.
> 3. After the embargo has passed, push out a new software release containing the fix.
> 4. Send email announcement on jruby-user mailing list containing source patch for most recent release.
> 5. Post an announcement on jruby.org and list below.
Can we get something like this added?
It is https://bugs.ruby-lang.org/projects/ruby/wiki/SecurityFixProcess
We don't have time schedule.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the current Ruby security page with the JRuby security page and the linked Ruby SecurityFixProcess. Add a clear disclosure procedure and time schedule to the relevant security documentation, then verify that the published page explains the reporting, embargo, release, and announcement steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100