You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Andreas Auernhammer baec331e84 crypto: add functions for sealing/unsealing the etag for SSE (#6618) ... This commit adds two functions for sealing/unsealing the etag (a.k.a. content MD5) in case of SSE single-part upload. Sealing the ETag is neccessary in case of SSE-S3 to preserve the security guarantees. In case of SSE-S3 AWS returns the content-MD5 of the plaintext object as ETag. However, we must not store the MD5 of the plaintext for encrypted objects. Otherwise it becomes possible for an attacker to detect equal/non-equal encrypted objects. Therefore we encrypt the ETag before storing on the backend. But we only need to encrypt the ETag (content-MD5) if the client send it - otherwise the client cannot verify it anyway.		6 years ago
..
config.go	…
doc.go	…
error.go	…
header.go	…
header_test.go	…
key.go	crypto: add functions for sealing/unsealing the etag for SSE (#6618)	6 years ago
key_test.go	crypto: add functions for sealing/unsealing the etag for SSE (#6618)	6 years ago
kms.go	…
kms_test.go	…
metadata.go	crypto: add functions for sealing/unsealing the etag for SSE (#6618)	6 years ago
metadata_test.go	crypto: add functions for sealing/unsealing the etag for SSE (#6618)	6 years ago
sse.go	…
sse_test.go	…
vault.go	…