From d28df9d384cb9c5e353437aa5a4a32ca90b4be21 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sun, 20 Jan 2013 20:37:10 +0000 Subject: [PATCH] Added a comment --- ...mment_8_0fa68d584ee7f6b5c9058fba7e911a11._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/special_remotes/S3/comment_8_0fa68d584ee7f6b5c9058fba7e911a11._comment diff --git a/doc/special_remotes/S3/comment_8_0fa68d584ee7f6b5c9058fba7e911a11._comment b/doc/special_remotes/S3/comment_8_0fa68d584ee7f6b5c9058fba7e911a11._comment new file mode 100644 index 0000000000..6997719d17 --- /dev/null +++ b/doc/special_remotes/S3/comment_8_0fa68d584ee7f6b5c9058fba7e911a11._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="68.119.100.5" + subject="comment 8" + date="2013-01-20T20:37:09Z" + content=""" +If encryption is not used, the files are stored in S3 as-is, and can be accessed directly. They are stored in a hashed directory structure with the names of their key used, rather than the original filename. To get back to the original filename, a copy of the git repo would also be needed. + +With encryption, you need the gpg key used in the encryption, or, for shared encryption, a symmetric key which is stored in the git repo. + +See [[future proofing]] for non-S3 specific discussion of this topic. +"""]]