[
https://issues.apache.org/jira/browse/TIKA-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460813#comment-17460813
]
Lewis John McGibbney commented on TIKA-3616:
--------------------------------------------
Hi Tim,
I’m not familiar with the downstream release process for the various Docker
artifacts.
Publishing the Helm chart is a walk in the park but entirely conditional
upon the Docker artifact.
Here’s the release process
https://wiki.apache.org/confluence/display/TIKA/Release+Process+for+tika-helm
Can I make the helm release? Absolutely.
--
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc
> 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)
