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

fixed markup

Browse source
This commit is contained in:
Ilya_Shlyakhter 2018-12-04 18:58:04 +00:00 committed by admin
parent 00ccf952e4
commit 5c510f6937
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/todo/encrypting_URLs.mdwn
View file

@ -3,7 +3,7 @@ E.g. record the URL as encryptedurl://key_id/[base64-encoded encryption of the o
Many cloud services let you create a pre-signed URL for a non-public file. Anyone with the URL can get the file, so the URL is "public" in that sense; Many cloud services let you create a pre-signed URL for a non-public file. Anyone with the URL can get the file, so the URL is "public" in that sense;
but you only share the URL with intended recipient(s), not the public. Or you might store files in a bucket that can be publicly read but not listed, and but you only share the URL with intended recipient(s), not the public. Or you might store files in a bucket that can be publicly read but not listed, and
store files under paths like s3://mybucket/<randomstring>/myfile ; the URL is "public" but in practice it can't be guessed. store files under paths like s3://mybucket/randomstring/myfile ; the URL is "public" but in practice it can't be guessed.
If the URLs could be stored encrypted in the git-annex branch, one could track such files using the ordinary web remote. One could use an S3 export-tree If the URLs could be stored encrypted in the git-annex branch, one could track such files using the ordinary web remote. One could use an S3 export-tree
remote to share a directory with specific recipient(s), without them needing either AWS credentials or git-annex. remote to share a directory with specific recipient(s), without them needing either AWS credentials or git-annex.