Log4j logging files in Solr are too old. Replacing with latest to avoid security concerns #313
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
…id security concerns
|
I will resume work on Monday and am not expecting this to work yet as I haven't attempted |
|
@joecorall raised a point that we could upgrade to Solr 9.x, maybe that's the route forward? https://islandora.slack.com/archives/C03472QEUM8/p1701358102239509 |
|
Okay I'll close this PR then as upgrading to Solr 9.x sounds like the community solution. @nigelgbanks or @joecorall Are either of you opening up a new issue to this effect and won't the current Drupal schema be impacted by this? |
Closed
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.
WIP for upgrading LOG4J logging files that are 2.17.x vs latest 2.22.0. This is a concern for security and CVEs. Will test shortly.