The checksum validation activity assumes that checksums in the provided metadata will be MD5. However, the eCH-0160 standard states that MD5, SHA-256, SHA-512, and SHA-1 are all permissible. Some of the sample packages that we have use SHA-256, and therefore fail on checksum validation.
To Reproduce
Steps to reproduce the behavior:
Upload a sample package with non-MD5 checksums (e.g. GEVER)
See it fail!
Expected behavior
The activity should support all valid checksum algorithms. In the metadata file, the checksum's algorithm is defined:
Describe the bug
The checksum validation activity assumes that checksums in the provided metadata will be MD5. However, the eCH-0160 standard states that MD5, SHA-256, SHA-512, and SHA-1 are all permissible. Some of the sample packages that we have use SHA-256, and therefore fail on checksum validation.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The activity should support all valid checksum algorithms. In the metadata file, the checksum's algorithm is defined:
The activity should check the
pruefalgorithmus
tag to determine the type of checksum and check using the correct algorithm.Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.