You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It supports a collection of different hashing algorithms but the default is CRC-64/NVME which the System.IO.Hashing package does not support. The default means if an object was uploaded without a checksum, using an older SDK, S3 automatically generates a CRC-64/NVME checksum at the service level. Objects can also get a CRC-64/NVME checksum if they use another language that does support CRC-64/NVME like Go. This puts .NET at a disadvantage because users that are downloading with .NET objects that have a CRC-64/NVME checksum have the data integrity check skipped.
Curious what the .NET team's appetite is for adding CRC-64/NVME support in System.IO.Hashing. It has a CRC64 implementation for ECMA-182 today. Depending how this GitHub issue API request is handled that could solve the S3 need. #78063
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Amazon S3 recently launched new data integrity checks when uploading and download objects. https://docs.aws.amazon.com/AmazonS3/latest/userguide/checking-object-integrity.html. For context I'm a maintainer of the AWS .NET SDK.
It supports a collection of different hashing algorithms but the default is
CRC-64/NVME
which the System.IO.Hashing package does not support. The default means if an object was uploaded without a checksum, using an older SDK, S3 automatically generates a CRC-64/NVME checksum at the service level. Objects can also get aCRC-64/NVME
checksum if they use another language that does supportCRC-64/NVME
like Go. This puts .NET at a disadvantage because users that are downloading with .NET objects that have aCRC-64/NVME
checksum have the data integrity check skipped.Curious what the .NET team's appetite is for adding
CRC-64/NVME
support in System.IO.Hashing. It has a CRC64 implementation for ECMA-182 today. Depending how this GitHub issue API request is handled that could solve the S3 need. #78063Beta Was this translation helpful? Give feedback.
All reactions