[GH-ISSUE #584] Failed to upload/copy with SSE_C and SSE_KMS #331

New issue

Closed

opened 2026-03-04 01:44:28 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:44:28 +03:00

Owner

Originally created by @ggtakec on GitHub (May 7, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/584

Additional Information

Version of s3fs being used (s3fs --version)
- Amazon Simple Storage Service File System V1.80(commit:8de992d)
Version of fuse being used (pkg-config --modversion fuse)
- 2.9.4(This problem is not dependent on the version of fuse)
System information (uname -a)
- n/a(This problem is not dependent on the version of OS)
Distro (cat /etc/issue)
- n/a(This problem is not dependent on the version of OS)
s3fs command line used (if applicable)

1) s3fs <bucket> /mnt/s3 -o allow_other,enable_content_md5,use_sse=custom:<sse custom key path>
2) s3fs <bucket> /mnt/s3 -o allow_other,enable_content_md5,use_sse=kmsid:<KMS ID ARN>

/etc/fstab entry (if applicable):
- n/a
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
- n/a

Details about issue

I confirmed the problem when checking PR of #486.

SSE_C and SSE_KMS that return ETag that is not object MD5
The ETAG when using SSE_C and SSE_KMS does not reflect the MD5 we sent
SSE_C: http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html
SSE_KMS is ignored in the above, but in the following it states the same in the highlights:
http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html

We also detected problems related to the above.

When rename an object of SSE_C, it is time to give the wrong header (SSE related).

Originally created by @ggtakec on GitHub (May 7, 2017). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/584 #### Additional Information - Version of s3fs being used (s3fs --version) - Amazon Simple Storage Service File System V1.80(commit:8de992d) - Version of fuse being used (pkg-config --modversion fuse) - 2.9.4(This problem is not dependent on the version of fuse) - System information (uname -a) - n/a(This problem is not dependent on the version of OS) - Distro (cat /etc/issue) - n/a(This problem is not dependent on the version of OS) - s3fs command line used (if applicable) ``` 1) s3fs <bucket> /mnt/s3 -o allow_other,enable_content_md5,use_sse=custom:<sse custom key path> 2) s3fs <bucket> /mnt/s3 -o allow_other,enable_content_md5,use_sse=kmsid:<KMS ID ARN> ``` - /etc/fstab entry (if applicable): - n/a - s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) - n/a #### Details about issue I confirmed the problem when checking PR of #486. - SSE_C and SSE_KMS that return ETag that is not object MD5 The ETAG when using SSE_C and SSE_KMS does not reflect the MD5 we sent SSE_C: http://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html SSE_KMS is ignored in the above, but in the following it states the same in the highlights: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingKMSEncryption.html We also detected problems related to the above. - When rename an object of SSE_C, it is time to give the wrong header (SSE related).

kerem

2026-03-04 01:44:28 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-04 01:44:30 +03:00

Author

Owner

@ggtakec commented on GitHub (May 7, 2017):

This issue is fixed by #585, but if you find bugs about this problem yet, please reopen this.

@ggtakec commented on GitHub (May 7, 2017): This issue is fixed by #585, but if you find bugs about this problem yet, please reopen this.

kerem referenced this issue

2026-03-04 01:54:06 +03:00

[PR #331] [MERGED] Address various clang warnings #1465