jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amit Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)
Date Fri, 03 Mar 2017 04:47:45 GMT

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

Amit Jain commented on JCR-4115:
--------------------------------

If there are no objections I would commit this change by Monday (6th March) and initiate an
unstable release 2.15.1

> Don't use SHA-1 for new DataStore binaries (Jackrabbit)
> -------------------------------------------------------
>
>                 Key: JCR-4115
>                 URL: https://issues.apache.org/jira/browse/JCR-4115
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>            Reporter: Thomas Mueller
>            Assignee: Amit Jain
>              Labels: candidate_jcr_2_10, candidate_jcr_2_12, candidate_jcr_2_14, candidate_jcr_2_4,
candidate_jcr_2_6, candidate_jcr_2_8
>             Fix For: 2.16
>
>         Attachments: JCR-4115b.patch, JCR-4115c.patch, JCR-4115.patch
>
>
> A collision for SHA-1 has been published. We still use SHA-1 for the FileDataStore, and
I believe the S3 DataStore right now. Given there is a collision, we should switch to a stronger
algorithm, for example SHA-256, for new binaries.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message