[
https://issues.apache.org/jira/browse/LOG4J2-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470635#comment-17470635
]
Ralph Goers commented on LOG4J2-3325:
-------------------------------------
With our previous release process the hashes could be generated one of two
ways. What you are seeing with 2.17.0 used the gpg command on a Mac to generate
the hash. The hash is perfectly valid in that the value is correct. With 2.17.1
we have automated the generation of the hash. However, it is still not
"correct" as it should have the file name follow the hash value. We are still
determining how to get the tool to do that.
In any case, the hash values are valid so this isn't a problem.
> hashes are wrong represented
> ----------------------------
>
> Key: LOG4J2-3325
> URL: https://issues.apache.org/jira/browse/LOG4J2-3325
> Project: Log4j 2
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 2.15.0
> Reporter: Pierre Gronau
> Priority: Minor
>
> https://archive.apache.org/dist/logging/log4j/2.15.0/apache-log4j-2.15.0-bin.tar.gz.sha512
> content
> apache-log4j-2.15.0-bin.tar.gz: C0E2D704 D720BFFC 99520E5D FBF860BA 3CB7F8A3
> 4C16A1CA A8CE3561 8370FF06 C19E3DC6 4FC258AD 45D43086 90551BF3 4B3ECB7A
> CC0848AA 12615F46 398CDA4A
> it SHOULD be represented like in 2.17.1
> [https://archive.apache.org/dist/logging/log4j/2.17.1/apache-log4j-2.17.1-bin.tar.gz.sha512]
> b7e948df6c6f57d903d990de2cc0270c1537b711285e9b6b91280db6ace38418fced713785b2c20512dd9a4238c2d1d0ceb414d9936df2ca110ff14993ae04dc
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
