You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/02/24 08:23:44 UTC

[jira] [Commented] (OAK-5827) Don't use SHA-1 for new DataStore binaries

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

Chetan Mehrotra commented on OAK-5827:
--------------------------------------

I think we can change hash algorithm and see affect on blobId etc. It can be safely done on existing setup also and would be used for only new binaries. 

> Don't use SHA-1 for new DataStore binaries
> ------------------------------------------
>
>                 Key: OAK-5827
>                 URL: https://issues.apache.org/jira/browse/OAK-5827
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Thomas Mueller
>
> A [collision for SHA-1|https://www.schneier.com/blog/archives/2017/02/sha-1_collision.html] 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)