[
https://issues.apache.org/jira/browse/HDDS-13668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-13668:
-------------------------------
Description:
See TODO in
[https://github.com/apache/ozone/blob/93fad7c77279b6ec9b6261189d026dd8a1c0c327/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/signature/StringToSignProducer.java#L340]
Currently, we don't implement x-amz-content-sha256 validation for both single
and multi chunks upload. The multi chunks upload validation is addressed in
HDDS-12542. This task is to support single signed chunk upload verification
(i.e. when {{x-amz-content-sha256}} actually contains the hash instead of
{{UNSIGNED-PAYLOAD}} or other multi chunk header
{{{}STREAMING-AWS4-HMAC-SHA256-PAYLOAD{}}}, etc).
The expected outcome is that signature issues like HDDS-12871 should pass after
implementing the single signed chunk upload. This also need to be accompanied
with the S3 integration tests / acceptance tests.
Currently we already have DigestInputStream with MD5 for ETag calculation, the
main challenge would be to also calculate other related digest (e.g. SHA-256 in
this case)
was:
See TODO in
[https://github.com/apache/ozone/blob/93fad7c77279b6ec9b6261189d026dd8a1c0c327/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/signature/StringToSignProducer.java#L340]
Currently, we don't implement x-amz-content-sha256 validation for both single
and multi chunks upload. The multi chunks upload validation is addressed in
HDDS-12542. This task is to support single signed chunk upload verification
(i.e. when {{x-amz-content-sha256}} actually contains the hash instead of
{{UNSIGNED-PAYLOAD}} or other multi chunk header
{{{}STREAMING-AWS4-HMAC-SHA256-PAYLOAD{}}}, etc).
The expected outcome is that signature issues like HDDS-12871 should pass after
implementing the single signed chunk upload. This also need to be accompanied
with the S3 integration tests / acceptance tests.
> Support S3 signed single chunks payload verification
> ----------------------------------------------------
>
> Key: HDDS-13668
> URL: https://issues.apache.org/jira/browse/HDDS-13668
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Priority: Major
>
> See TODO in
> [https://github.com/apache/ozone/blob/93fad7c77279b6ec9b6261189d026dd8a1c0c327/hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/signature/StringToSignProducer.java#L340]
> Currently, we don't implement x-amz-content-sha256 validation for both single
> and multi chunks upload. The multi chunks upload validation is addressed in
> HDDS-12542. This task is to support single signed chunk upload verification
> (i.e. when {{x-amz-content-sha256}} actually contains the hash instead of
> {{UNSIGNED-PAYLOAD}} or other multi chunk header
> {{{}STREAMING-AWS4-HMAC-SHA256-PAYLOAD{}}}, etc).
> The expected outcome is that signature issues like HDDS-12871 should pass
> after implementing the single signed chunk upload. This also need to be
> accompanied with the S3 integration tests / acceptance tests.
> Currently we already have DigestInputStream with MD5 for ETag calculation,
> the main challenge would be to also calculate other related digest (e.g.
> SHA-256 in this case)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
