Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-26514

Checksum attributes listed inconsistently and in a different order

Details

    • 2

    Description

      On H2, I noticed Metadata checksum (Maven) listed in SHA512, SHA1, MD5, SHA256. This struck me as a weird order with MD5 in the middle to say the least.
      I checked Orient and the order was SHA1, SHA512, SHA256 and M5.
      I checked another component and that was the same, but checked H2 again and this time their order was different than both the above reports.
      As far as I can tell, Orient is consistently ordered but newDB is not (and none of the orderings I saw matched Orient).

      If no-one cares, I suggest we do SHA1, SHA256, SHA512, M5 too (I am not sure why Orient is ordered as it is either, but increasing "value" of SHA makes sense to me).

      Here's the components I tested:

      In theory you can download them both and see, but since it's inconsistent I have no idea if that'll work as it did with me or not.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jtom Joe Tom
            Michael Oliverio Michael Oliverio
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              tigCommentSecurity.panel-title