From 5c510f6937c2c8c1203bf0930a1f84b2e7a1a295 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 4 Dec 2018 18:58:04 +0000 Subject: [PATCH] fixed markup --- doc/todo/encrypting_URLs.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/todo/encrypting_URLs.mdwn b/doc/todo/encrypting_URLs.mdwn index a733254bb7..1b8fe9e103 100644 --- a/doc/todo/encrypting_URLs.mdwn +++ b/doc/todo/encrypting_URLs.mdwn @@ -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; 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//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 remote to share a directory with specific recipient(s), without them needing either AWS credentials or git-annex.