diff options
author | 2013-01-15 16:44:03 -0400 | |
---|---|---|
committer | 2013-01-15 16:44:03 -0400 | |
commit | 3fb5817c92a21b0b133ba6c1a5fb11d9f6ff1c6f (patch) | |
tree | 1f7dfbe8ae283781a7eac601751a0f857bc7f76e | |
parent | 1dc9fa4bbdb61207445df7c890b3573bbb16a66c (diff) | |
parent | 738bae92f34f23bf8e44a7d18928729c75ed8f12 (diff) |
Merge branch 'master' of ssh://git-annex.branchable.com
2 files changed, 21 insertions, 0 deletions
diff --git a/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_1_e10363a912953a646b87c824d1c6e5d4._comment b/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_1_e10363a912953a646b87c824d1c6e5d4._comment new file mode 100644 index 000000000..ea2b1fbf3 --- /dev/null +++ b/doc/bugs/git-annex:_Not_in_a_git_repository._/comment_1_e10363a912953a646b87c824d1c6e5d4._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.7.238" + subject="comment 1" + date="2013-01-15T20:20:22Z" + content=""" +Sounds like a permissions error. Take a look at the repository in `~/Desktop/annex/` or `~/annex/` , and see if it contains files owned by root, or has bad directory permissions that would prevent your normal user from accessing it. Don't forget to check in its `.git` directory. + +I'd recommend not running the git-annex webapp as root. (There may be valid use cases for root to use git-annex in command-line mode.) +"""]] diff --git a/doc/forum/No_SSL_traffic_for_S3__63__/comment_1_f509bf273896180e6df8c771438dd093._comment b/doc/forum/No_SSL_traffic_for_S3__63__/comment_1_f509bf273896180e6df8c771438dd093._comment new file mode 100644 index 000000000..808d4c035 --- /dev/null +++ b/doc/forum/No_SSL_traffic_for_S3__63__/comment_1_f509bf273896180e6df8c771438dd093._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.7.238" + subject="comment 1" + date="2013-01-15T20:25:42Z" + content=""" +<http://hackage.haskell.org/package/hS3> is a Haskell library for S3, which git-annex uses. It does not support HTTPS. I'm sure its author would appreciate help, or maybe even just gentle motivation. + +FWIW, I think that S3's authorization is designed to be pretty secure even over an un-encrypted transport. +It uses HMAC to sign the request with your AWS credentials securely, and includes a date that is hopefully used to avoid replay attacks. +"""]] |