Self-hosted Sentry is not vulnerable to log4shell #1203
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
BYK
reviewed
Dec 15, 2021
| @@ -58,3 +58,4 @@ Where you replace `83b1380` with the sha you want to use. | |||
|
|
|||
| [build-status-image]: https://github.com/getsentry/self-hosted/workflows/test/badge.svg | |||
| [build-status-url]: https://git.io/JUYkh | |||
|
|
|||
There was a problem hiding this comment.
🤣 Why not literally add a disclaimer in the readme: Sentry is not vulnerable to log4shell
There was a problem hiding this comment.
Because nobody is going to care in a month? 0, 1, infinity.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 is a dummy PR to work around limitations with the automated changelog system we are using. Please see #1196 for discussion.