From 8839c23f5b112b48125d757e3f8aa68ba10168d8 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" Date: Thu, 22 Jan 2015 01:05:56 +0000 Subject: [PATCH 1/8] Added a comment --- ...ent_1_b7b4819211910556838ec37bc2b6b37b._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment diff --git a/doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment b/doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment new file mode 100644 index 0000000000..9077eada90 --- /dev/null +++ b/doc/design/v6/comment_1_b7b4819211910556838ec37bc2b6b37b._comment @@ -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. +"""]] From 125fb88e541e159d1a5c340e23cb95499ecfec59 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkWHj0RxNMfuwvFzo2d-V6vBKOYwW_Fnfk" Date: Thu, 22 Jan 2015 06:29:36 +0000 Subject: [PATCH 2/8] Added a comment: Update on determining disk usage --- ...nt_13_8e0e86ae716ff018025808f417e1f7f6._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/gadu_-_git-annex_disk_usage/comment_13_8e0e86ae716ff018025808f417e1f7f6._comment diff --git a/doc/forum/gadu_-_git-annex_disk_usage/comment_13_8e0e86ae716ff018025808f417e1f7f6._comment b/doc/forum/gadu_-_git-annex_disk_usage/comment_13_8e0e86ae716ff018025808f417e1f7f6._comment new file mode 100644 index 0000000000..b62b05ad89 --- /dev/null +++ b/doc/forum/gadu_-_git-annex_disk_usage/comment_13_8e0e86ae716ff018025808f417e1f7f6._comment @@ -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 +"""]] From de4eb2d24811b606d456f39202253559a4e0445b Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkWHj0RxNMfuwvFzo2d-V6vBKOYwW_Fnfk" Date: Thu, 22 Jan 2015 06:29:51 +0000 Subject: [PATCH 3/8] Added a comment: Update on determining disk usage --- ...nt_14_6279f238df5be485f1ac99f75242a325._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/gadu_-_git-annex_disk_usage/comment_14_6279f238df5be485f1ac99f75242a325._comment diff --git a/doc/forum/gadu_-_git-annex_disk_usage/comment_14_6279f238df5be485f1ac99f75242a325._comment b/doc/forum/gadu_-_git-annex_disk_usage/comment_14_6279f238df5be485f1ac99f75242a325._comment new file mode 100644 index 0000000000..7746b2538a --- /dev/null +++ b/doc/forum/gadu_-_git-annex_disk_usage/comment_14_6279f238df5be485f1ac99f75242a325._comment @@ -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:51Z" + 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 +"""]] From 9c232bfac0d4a547adbfd45139cac9444f6e21af Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkWHj0RxNMfuwvFzo2d-V6vBKOYwW_Fnfk" Date: Thu, 22 Jan 2015 06:30:22 +0000 Subject: [PATCH 4/8] removed --- ...nt_14_6279f238df5be485f1ac99f75242a325._comment | 14 -------------- 1 file changed, 14 deletions(-) delete mode 100644 doc/forum/gadu_-_git-annex_disk_usage/comment_14_6279f238df5be485f1ac99f75242a325._comment diff --git a/doc/forum/gadu_-_git-annex_disk_usage/comment_14_6279f238df5be485f1ac99f75242a325._comment b/doc/forum/gadu_-_git-annex_disk_usage/comment_14_6279f238df5be485f1ac99f75242a325._comment deleted file mode 100644 index 7746b2538a..0000000000 --- a/doc/forum/gadu_-_git-annex_disk_usage/comment_14_6279f238df5be485f1ac99f75242a325._comment +++ /dev/null @@ -1,14 +0,0 @@ -[[!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:51Z" - 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 -"""]] From 53455fe723cffe67666f268856c10b699c0d5dbd Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw" Date: Thu, 22 Jan 2015 18:11:35 +0000 Subject: [PATCH 5/8] --- ...for_Google_cloud_storage_remote__63__.mdwn | 29 +++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn diff --git a/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn b/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn new file mode 100644 index 0000000000..5b0eff50fe --- /dev/null +++ b/doc/bugs/Forcing_https_for_Google_cloud_storage_remote__63__.mdwn @@ -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. From 202f5499263955bab86670c9b203ac21acb8ea2b Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw" Date: Thu, 22 Jan 2015 18:24:34 +0000 Subject: [PATCH 6/8] Added a comment: Additional experiment --- ...ment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment diff --git a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment new file mode 100644 index 0000000000..c16de56a4a --- /dev/null +++ b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment @@ -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:24:34Z" + 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. + + +"""]] From 22a7fd020cdce78fab849c7bc10c879f071c5a6b Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw" Date: Thu, 22 Jan 2015 18:26:18 +0000 Subject: [PATCH 7/8] Added a comment: Additional experiment --- ...ment_2_94654cd68a183a1d6210aa4ca13aca70._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_94654cd68a183a1d6210aa4ca13aca70._comment diff --git a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_94654cd68a183a1d6210aa4ca13aca70._comment b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_94654cd68a183a1d6210aa4ca13aca70._comment new file mode 100644 index 0000000000..2420e3d0cb --- /dev/null +++ b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_2_94654cd68a183a1d6210aa4ca13aca70._comment @@ -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. + + +"""]] From 7d0e5f9fc902f8f5ff9ae7bcfce39f074f6d5062 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw" Date: Thu, 22 Jan 2015 18:26:45 +0000 Subject: [PATCH 8/8] removed --- ...ment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment | 13 ------------- 1 file changed, 13 deletions(-) delete mode 100644 doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment diff --git a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment b/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment deleted file mode 100644 index c16de56a4a..0000000000 --- a/doc/bugs/How_to_use_a_DRA_bucket_in_Google_cloud_storage__63__/comment_1_b8ad7252ff3bc8c678b6b41fbfe03434._comment +++ /dev/null @@ -1,13 +0,0 @@ -[[!comment format=mdwn - username="https://www.google.com/accounts/o8/id?id=AItOawkXzY87FdO942LR-qNyJFeCth0LjWORNuw" - nickname="Rob" - subject="Additional experiment" - date="2015-01-22T18:24:34Z" - 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. - - -"""]]