diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-04-03 14:34:00 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-04-03 14:34:00 -0400 |
| commit | 83acc9ba52ecba85180355a8c08311bd4826ed0f (patch) | |
| tree | 750afe3c10eff8fa81b883e712517bfede5dfeef /doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn | |
| parent | ee313074ed65145692acff1402e6262c2ea4b437 (diff) | |
encryption design document
Diffstat (limited to 'doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn')
| -rw-r--r-- | doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn index 0ec66652e..1980a8f44 100644 --- a/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn +++ b/doc/bugs/S3_bucket_uses_the_same_key_for_encryption_and_hashing.mdwn @@ -3,3 +3,6 @@ While using HMAC instead of "plain" hash functions is inherently more secure, it Also, ttbomk, HMAC needs two keys, not one. Are you re-using the same key twice? Compability for old buckets and support for different ones can be maintained by introducing a new option and simply copying over the encryption key's identifier into this new option should it be missing. + +> See [[design/encryption]]. I don't think this bug needs to be kept +> open. [[done]] --[[Joey]] |