mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

blog for the day

Browse source
This commit is contained in:
Joey Hess 2012-09-26 16:45:24 -04:00
parent f9237df144
commit 521b64f7ee
2 changed files with 24 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

23
doc/design/assistant/blog/day_92__S3.mdwn Normal file
View file

@ -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.