You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Michael Mior (JIRA)" <ji...@apache.org> on 2017/09/04 14:57:00 UTC

[jira] [Commented] (CALCITE-1972) Create .sha512 and .md5 digests for release artifacts

    [ https://issues.apache.org/jira/browse/CALCITE-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152684#comment-16152684 ] 

Michael Mior commented on CALCITE-1972:
---------------------------------------

Fixed in [f10950b58|https://github.com/apache/calcite/commit/f10950b58b66954eadc7c275e9549fb9dcc02864].

> Create .sha512 and .md5 digests for release artifacts
> -----------------------------------------------------
>
>                 Key: CALCITE-1972
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1972
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Michael Mior
>             Fix For: 1.14.0
>
>
> Following CALCITE-1329 we currently generate a .mds file containing multiple digests, but breaches Apache policy for the file names that can be generated. We should instead generate a file with .sha512 suffix containing a SHA512 digest.
> No need to generate MD5 or SHA1; these are no longer secure.
> Steps:
> * in pom.xml, modify the checksum-maven-plugin configuration;
> * in HOWTO.md, remove the steps to generate the .mds file;
> * in site/downloads/index.md, modify the "assign digest" logic for releases 1.14 and later.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)