Add vulnerability warning to README #966
Merged
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
This commit adds a warning notice about CVE-2015-9284 and directs the user to the FAQ where they can find steps to mitigate it.
|
@tmilewski any chance of a merge on this? It would be good to put a warning on the front page of the repo for new users/anyone who comes looking for mitigation techniques. |
|
Paging anyone @omniauth - this should literally take 10 seconds to review! |
|
|
BobbyMcWho
approved these changes
Nov 20, 2019
There was a problem hiding this comment.
Sorry this took so long @CHTJonas, I just recently got maintainer rights to this repo, and I'm working through the backlog of issues and PR's as I can find time to.
Thank you for contributing!
|
Closing and reopening to trigger a CI job based on current master. |
|
Thanks! |
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.
This PR adds a warning notice regarding CVE-2015-9284 and directs the user to the FAQ where they can find steps to mitigate it.
This addresses some of the suggestions raised by folks in #809.