From cb69574f966630504fe1cb62e0a677aac51b746d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 5 Jun 2015 13:29:54 -0400 Subject: [PATCH] comment --- ...omment_3_96c8bcb545578280dc02c00d82978f77._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/credentials-less_access_to_s3/comment_3_96c8bcb545578280dc02c00d82978f77._comment diff --git a/doc/todo/credentials-less_access_to_s3/comment_3_96c8bcb545578280dc02c00d82978f77._comment b/doc/todo/credentials-less_access_to_s3/comment_3_96c8bcb545578280dc02c00d82978f77._comment new file mode 100644 index 0000000000..52802de2ae --- /dev/null +++ b/doc/todo/credentials-less_access_to_s3/comment_3_96c8bcb545578280dc02c00d82978f77._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2015-06-05T17:28:52Z" + content=""" +Based on + +and my testing, S3 does not default to allowing public access to buckets. So, +this seems like something that it makes sense for the user to +manually configure when setting up a s3 remote. +"""]]