This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • SHA256 checksums for checking uploads

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: usage

...

A user must be able to enter the algorithm to use. The available algorithms must be configured through automatic discovery by the spring framework. A certain check algorithm will only work if the algorithm code is available in the management server and in the SSVM. In the present specs of java all implementations must provide at least {MD5, SHA-1, SHA-256}.

Use

The parameter containing the checksum will be considered a MD5sum if it is not prefixed and just a plain ascii/utf8 representation of a hexadecimal string. If it is required to use another algorithm the hexadecimal string is to be prefixed with a string of the form, "{<algorithm>}", not including the double quotes. In this <algorithm> is the exact string representing the java supported algorithm, i.e. MD5 or SHA-256. Note that java does not contain an algorithm called SHA256 or one called sha-256, only SHA-256.

UI

At the moment only the Volume upload Form has a field for entering a checksum value. This field will be abused by letting the user enter a checksum-type prefix to the checksum value.

...