jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (JCR-4115) Don't use SHA-1 for new DataStore binaries (Jackrabbit)
Date Fri, 24 Feb 2017 09:24:44 GMT

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

Thomas Mueller edited comment on JCR-4115 at 2/24/17 9:24 AM:
--------------------------------------------------------------

Not sure if AbstractDataStore.HmacSHA1 is also affected or not. Probably not, because it uses
DataIdentifier.toString() as the input.


was (Author: tmueller):
Not sure if AbstractDataStore.HmacSHA1 is also affected or not.

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