CloudMarc commented on PR #5364:
URL: https://github.com/apache/solr/pull/5364#issuecomment-7047111711
> +1 to the PR and thanks for contributing
>
> I don't think there's any urgency as it's something a user can do from
their end with SOLR_OPTS env var or `--jvm-opts` CLI option. If a user is
proactive/alert to Java4Shell like you, they can do this _now_. I expect Docker
Inc & Eclipse Temurin (JDK) to release an update much faster than we can do so.
You can also expect an update to our website shortly to advise users on what I
said and more.
Thanks for the review! On the changelog note, I want to make sure I address
the right thing. The bot's own reasoning ("a security fix with user-visible
implications") actually argues for type: security, which is what's there now,
matching SOLR-17888's precedent (the Tika CVE mitigation entry).
Did you want the type changed to `fixed` specifically, or was there
something else about the fragment you'd flag?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]