Elbencho uses X_AMZ_CHECKSUM_CRC64NVME when no checksum algorithm was requested

[shustinm]

A simple object or metadata write uses this checksum algorithm, even though no --s3checksumalgo was provided.

[breuner]

Hi @shustinm,
might be related to the default behavior change that was announced here?
aws/aws-sdk-cpp#3253

Since the update to an SDK version higher than the one mentioned in the announcement, the S3 client config of elbencho sets the default checksum calculation to "only when required", so I'm guessing this might be one of the cases where the SDK (devs) defined that it is required:

elbencho/source/toolkits/S3Tk.cpp

Line 159 in 8fb043f

config.checksumConfig.requestChecksumCalculation =

[breuner]

Hi @shustinm , shall we leave this issue open or can we close it?