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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2015-01-22 14:53:09 -04:00
commit d1ac9904b8
4 changed files with 70 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

29
doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn Normal file
View file

@ -0,0 +1,29 @@
### Please describe the problem.
A special remote for Google cloud storage would appear to send the developer keys in the clear.
Obviously the content itself can be secured with the encryption but sending the auth keys in
the clear permits anybody listening (i.e. at a public WiFi access point) to gain r/w access to
the user's GCS store.
### What steps will reproduce the problem?
Setup a new special remote:
git annex initremote gcs type=S3 chunk=2MiB encryption=none host=storage.googleapis.com bucket=gitannex
...
git move --to=gcs blah
Capture packets. Watch the developer keys go by in the headers. And in this case, see the content too because there's no
encryption turned on. But I believe that I know how to fix this.
I tried to persuade `git annex` to use a SSL connection but without encouraging results:
git annex initremote gcs type=S3 chunk=2MiB port=443 host=storage.googleapis.com bucket=gitannex
initremote gcs (checking bucket...) git-annex: ErrorClosed
### What version of git-annex are you using? On what operating system?
Debian wheezy, git-annex version: 5.20141024~bpo70+1
### Please provide any additional information below.

13
doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_94654cd68a183a1d6210aa4ca13aca70._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw"
nickname="Rob"
subject="Additional experiment"
date="2015-01-22T18:26:17Z"
content="""
I tried unuccessfully on GCS DRA bucket gitannex-dra:
git annex initremote gcs type=S3 chunk=2MiB encryption=none host=storage.googleapis.com bucket=gitannex-dra storageclass=DURABLE_REDUCED_AVAILABILITY
initremote gcs (checking bucket...) git-annex: Invalid argument.
"""]]

14
doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U"
nickname="Richard"
subject="comment 1"
date="2015-01-22T01:05:56Z"
content="""
My gut feeling for incompatible changes in v6 is to somehow make v5 and below error out on all merges with a v6 repo.
Conversely, v6 git-annex running in v6 repos would transition all data while merging in v5 repos.
As a migration path for existing repos, you could move `git-annex` and `master` to `git-annex_v5` and `master_v5`. Once you are certain all known repos within that repo group are transitioned, either kill the v5 branches automagically or print info on cli/web UI on what needs to be run to get rid of them.
Having several plain git 1+ GiB repos (i.e. without any annex objects), I would love to transition after v6 and the migration paths have been hung a month or three to dry.
"""]]

14
doc/forum/gadu_-_git-annex_disk_usage/comment_13_8e0e86ae716ff018025808f417e1f7f6._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawkWHj0RxNMfuwvFzo2d-V6vBKOYwW_Fnfk"
nickname="Andrew"
subject="Update on determining disk usage"
date="2015-01-22T06:29:36Z"
content="""
I just had a look at this question today as I learn git-annex. I think the commands have changed since the last comment. However, there remain several ways to determine disk usage, for example in the folder `Music`
git annex info Music
but you could also use `du` with
du --human-readable --dereference Music
"""]]