summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2012-09-26 16:45:24 -0400
committerGravatar Joey Hess <joey@kitenet.net>2012-09-26 16:45:53 -0400
commitcb1913e6cddfa090bda8b860d9b4129d83cf2c83 (patch)
tree9fedbe974d337fb20f2a42fa3498e80cd2ad40b3
parent4e00f4e7e3b8c28feb02ea7c42fe95e58e209f4e (diff)
blog for the day
-rw-r--r--doc/design/assistant/blog/day_92__S3.mdwn23
-rw-r--r--doc/design/assistant/polls/prioritizing_special_remotes.mdwn2
2 files changed, 24 insertions, 1 deletions
diff --git a/doc/design/assistant/blog/day_92__S3.mdwn b/doc/design/assistant/blog/day_92__S3.mdwn
new file mode 100644
index 000000000..c3f275a86
--- /dev/null
+++ b/doc/design/assistant/blog/day_92__S3.mdwn
@@ -0,0 +1,23 @@
+Amazon S3 was the second most popular choice in the
+[[polls/prioritizing_special_remotes]] poll, and since I'm not sure how
+I want to support phone/mp3 players, I did it first.
+
+So I added a configurator today to easily set up an Amazon S3 repository.
+That was straightforward and didn't take long since git-annex already
+supported S3.
+
+The hard part, of course, is key distribution. Since the webapp so far
+can only configure the shared encryption method, and not fullblown gpg keys,
+I didn't feel it would be secure to store the S3 keys in the git repository.
+Anyone with access to that git repo would have full access to S3 ... just not
+acceptable. Instead, the webapp stores the keys in a 600 mode file locally,
+and they're not distributed at all.
+
+When the same S3 repository is enabled on another computer, it prompts for
+keys then too. I did add a hint about using the IAM Management Console in
+this case -- it should be possible to set up users in IAM who can only
+access a single bucket, although I have not tried to set that up.
+
+---
+
+Also, more work on the standalone OSX app.
diff --git a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn
index 478453065..4ecee8e36 100644
--- a/doc/design/assistant/polls/prioritizing_special_remotes.mdwn
+++ b/doc/design/assistant/polls/prioritizing_special_remotes.mdwn
@@ -6,7 +6,7 @@ locally paired systems, and remote servers with rsync.
Help me prioritize my work: What special remote would you most like
to use with the git-annex assistant?
-[[!poll open=yes 14 "Amazon S3" 8 "Amazon Glacier" 6 "Box.com" 44 "My phone (or MP3 player)" 5 "Tahoe-LAFS" 3 "OpenStack SWIFT" 12 "Google Drive"]]
+[[!poll open=yes 14 "Amazon S3 (done)" 8 "Amazon Glacier" 6 "Box.com" 44 "My phone (or MP3 player)" 5 "Tahoe-LAFS" 3 "OpenStack SWIFT" 12 "Google Drive"]]
This poll is ordered with the options I consider easiest to build
listed first. Mostly because git-annex already supports them and they