jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amit Jain (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-5827) Don't use SHA-1 for new DataStore binaries
Date Thu, 09 Mar 2017 09:55:38 GMT

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

Amit Jain updated OAK-5827:
---------------------------
    Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 candidate_oak_1_6  (was:
)

> 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
>            Assignee: Amit Jain
>              Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, candidate_oak_1_6
>             Fix For: 1.7.0, 1.8
>
>         Attachments: OAK-5827b.patch, OAK-5827.patch
>
>
> 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)

Mime
View raw message