It seems like the Backblaze team has updated their S3 APIs to accept the new checksum algorithm header and thus doesn't produce the errors that were previously described. Although this repo didn't pin to less than 1.36 I thought it'd be best to keep versioning consistent throughout repos.