Recent comments posted to this site:
You can also use the --fast option to make git-annex use less entropy when generating the encryption key. That's a little less secure, but probably still secure enough.
For me, the git annex initremote amazon-s3 encryption=shared embedcreds=yes
[1] command hung for several minutes after printing
initremote amazon-s3 (encryption setup)
Turns out the problem was that I was low on entropy. Figured this out by running
gpg --gen-random 2
per this bug comment. According to this blog post a solution is to
sudo aptitude install rng-tools
sudo rngd -r /dev/urandom
The git annex initremote
command had finished by the time I found that solution, but I verified that it made gpg --gen-random 2
work.
System: Ubuntu 16.04 with Git Annex 5.20151208-1build1 installed via package manager.
[1] I'm using AWS credentials that are restricted to a specific bucket, so I'm not worried about the conjunction encryption=shared
and embedcreds=yes
.
@David_K @Joe, it's finally possible to publish annexed files to S3 while
preserving filenames, using the new git annex export
command!
See publishing your files to the public.
I've updated the proposed external special remote protocol to avoid the whitespace concerns. Not wild about needing a separate EXPORT request, which will probably get shoved into a global variable in most implementations. But it does avoid needing to use some kind of encoding, which would complicate implementations more, I feel.
Since external special remote protocol broken by key with spaces was fixed, the Key can't contain spaces any longer.
The File could still contain spaces, eg when exporting from a direct mode repository where the worktree filename contains spaces.
In RENAMEEXPORT
, both OldName and NewName could contain spaces.
It should be possible to write a git-filter-branch
that converts
a repository from one tuning to aonther, but it would not be trivial, and
noone has done it yet. You'd still have to run it in every clone of the
repository. Tuned and non-tuned repositories can't interoperate.
IPFS now has an experimental feature for not duplicating file content in the ipfs store, which could be very helpful for this use. See description at https://github.com/ipfs/go-ipfs/issues/3397#issuecomment-284337564 .
To use this, git-annex needs to pass the
--nocopy
flag when runningipfs add
.