[jira] [Updated] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Updated] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/JCR-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated JCR-4115:
    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  (was: candidate_jcr_2_10 candidate_jcr_2_12 candidate_jcr_2_4 candidate_jcr_2_6 candidate_jcr_2_8)

> 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, 2.15.1
>         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