Why is the default checksum algorithm MD5? And how to be FIPS compliant with that?

[OliLay]

Hi,

as far as I can see, the default checksum algorithm (when not manually set to something else), is MD5, see e.g. here.
Why is this the default algorithm? We're having issues because our OpenSSL library has FIPS turned on, meaning trying to get a MD5 hash from it will not work. (actually, it ends in a SEGFAULT).
As far as I can see, we can set an explicit, different algorithm for every request, but it would be much better to be able either change the default checksum algorithm (e.g. as global option) or generally change the hardcoded default to something FIPS compliant.

Any thoughts on this? Is there an easier way to avoid MD5 when using the SDK?

Best regards

[jmklix]

@github-actions proposed-answer

I'm not sure of the exact reason as to why MD5 was chosen for the default checksum, but I would guess that it might have been the standard back when this sdk was originally written. You can also try using our high level transfer manager library called transfer. When using transfer manager you can set the checksum algorithm with checksumAlgorithm. Also transfer manager defaults to CRC32. Please let us know if you have any other questions about using this sdk.

[github-actions[bot]]

Hello! A team member has suggested the above comment as the likely answer to this discussion thread.

• If you agree, please upvote that comment, or click on Mark as answer. I will automatically mark the discussion as answered with upvoted comment, next time I check.

• If this answer does not help you, please downvote the answer instead and let us know why it was not helpful. I will add a label to this discussion to gain attention from the team.