Skip to content

Conversation

@ChrisHegarty
Copy link
Contributor

Backport of:

Copy link
Contributor

@pgomulka pgomulka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@costin costin self-requested a review December 18, 2021 19:56
Copy link
Member

@costin costin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ChrisHegarty ChrisHegarty changed the title [6.8] Upgrade to log4j 2.17.0 [6.8.22] Upgrade to log4j 2.17.0 Dec 18, 2021
@ChrisHegarty ChrisHegarty merged commit 71fcb50 into elastic:6.8 Dec 18, 2021
@ChrisHegarty ChrisHegarty deleted the 6.8_log4j_2.17.0 branch December 18, 2021 21:07
@boicehuang
Copy link
Contributor

boicehuang commented Dec 21, 2021

hello, I found "log4j-core-2.‎17.0.jar.sha1‎" should be "fe6e7a32c1228884b9691a744f953a55d0dd8ead", not "587127e2f8c5daaef9ba3806848675a1652959d3"

It will lead to check sha1 failure

https://github.com/elastic/elasticsearch/blob/v6.8.22/server/licenses/log4j-core-2.17.0.jar.sha1#L1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants