You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (JIRA)" <ji...@apache.org> on 2018/03/07 13:36:00 UTC

[jira] [Commented] (TIKA-2600) Don't use md5 checksum due to changes to the release distribuition policy

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

Tim Allison commented on TIKA-2600:
-----------------------------------

I'm pretty sure we discussed this at some point, but I can't quickly find what we decided.  Apologies if this is a duplicate issue...

Should we stop including md5 and swap SHA1 (with file ext: .sha) for SHA512 (with file ext: .sha512)?

> Don't use md5 checksum due to changes to the release distribuition policy
> -------------------------------------------------------------------------
>
>                 Key: TIKA-2600
>                 URL: https://issues.apache.org/jira/browse/TIKA-2600
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Blocker
>
> To plagiarize from PDFBOX-4142:
> The release distribution policy was changes with regard to the checksums to be used:
> Old policy :
> MUST provide a MD5-file
> SHOULD provide a SHA-file [SHA-512 recommended]
> New policy :
> MUST provide a SHA- or MD5-file
> SHOULD provide a SHA-file
> SHOULD NOT provide a MD5-file
> see http://www.apache.org/dev/release-distribution for further details



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)