[
https://issues.apache.org/jira/browse/IGNITE-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953476#comment-14953476
]
Konstantin Boudnik commented on IGNITE-1656:
--------------------------------------------
There's a simple way to deal with it once and for all (this is the HBase,
Hadoop approach). For all release artifacts you can run something like this:
{{for i in *.tar.gz; do echo $i; gpg --print-mds $i > $i.mds ; done}}
gpg produces a set of checksums, including all available SHA's and some others.
What's important is that gpg behaves the same way on all platforms, so
verification format issues will be non-existent.
> Get rid of md5 and sha1 in favor of sha512
> ------------------------------------------
>
> Key: IGNITE-1656
> URL: https://issues.apache.org/jira/browse/IGNITE-1656
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: ignite-1.4
> Reporter: Ivan Veselovsky
> Fix For: 1.5
>
>
> Description of the problem wrt sha1 is there:
> https://sites.google.com/site/itstheshappening/ .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
