[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460782#comment-17460782
]
Tim Allison commented on TIKA-3616:
-----------------------------------
We'll hit 72 hours since the beginning of the vote for 2.2.0 by the end of the
day today. We have gotten no -1 votes, so, so far, the vote looks like it will
be successful. I'll push the release and announce as soon as we hit 72 hours.
I hope that we'll be able to release an updated docker image asap (tomorrow?)
after the release of 2.2.0. [~dmeikle] will you have time to run this? Or
maybe [~lewismc]?
I've sent a draft of an official statement to the private pmc list for
feedback. I'll send that to user@tika and dev@tika unless there are objections
from fellow PMC members.
> Upgrade log4j2
> --------------
>
> Key: TIKA-3616
> URL: https://issues.apache.org/jira/browse/TIKA-3616
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
> Fix For: 2.1.1
>
>
> RCE...might be difficult to trigger in Tika, but why ask for a PoC...
> This only affects 2.x. We were still using the old log4j in 1.x
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
