You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2017/03/01 10:41:45 UTC
[jira] [Updated] (JCR-4115) Don't use SHA-1 for new DataStore
binaries (Jackrabbit)
[ https://issues.apache.org/jira/browse/JCR-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated JCR-4115:
--------------------------------
Fix Version/s: 2.16
> 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
> 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)