Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-4115

Don't use SHA-1 for new DataStore binaries (Jackrabbit)

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.16, 2.15.1, 2.14.2
    • None
    • None

    Description

      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.

      Attachments

        1. JCR-4115.patch
          3 kB
          Thomas Mueller
        2. JCR-4115b.patch
          6 kB
          Thomas Mueller
        3. JCR-4115c.patch
          8 kB
          Amit Jain

        Issue Links

        blocks

        Improvement - An improvement or enhancement to an existing feature or task. OAK-5827 Don't use SHA-1 for new DataStore binaries

        • Major - Major loss of function.
        • Closed
        breaks

        Bug - A problem which impairs or prevents the functions of the product. JCR-4149 change to drop SHA-1 requires version change

        • Major - Major loss of function.
        • Closed
        is duplicated by

        New Feature - A new feature of the product, which has yet to be developed. OAK-4810 FileDataStore: support SHA-2

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            amitjain Amit Jain
            thomasm Thomas Mueller
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment