Clarify intended use and vulnerability handling policy#213
Open
hsbt wants to merge 1 commit into
Open
Conversation
The README and the rdoc discouraged production use but did not say how reports are handled. State that WEBrick is intended for testing and local development and is not intended to receive traffic from untrusted sources, and that while security issues are fixed in the open through the ordinary bug fixing process, the developers do not operate a vulnerability handling process and do not request CVE IDs. #199 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Member
Author
|
@jeremyevans Could you look this? |
This file contains hidden or 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
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.
Follow-up to the discussion in #199. The README and the
lib/webrick.rbrdoc discouraged production use but said nothing about how reports are handled, so the basis for treating them as non-vulnerabilities had to be explained again in each discussion. Both documents now state that WEBrick is intended for testing and local development and is not intended to receive traffic from untrusted sources, and that while security issues are fixed in the open through the ordinary bug fixing process, the developers do not operate a vulnerability handling process for WEBrick and do not request CVE IDs. Documentation only, no code changes.Generated with Claude Code