summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar digiuser <digiuser@web>2015-06-23 23:01:50 +0000
committerGravatar admin <admin@branchable.com>2015-06-23 23:01:50 +0000
commit5695024b6d46a0674db5b07da7b7c996f2a10337 (patch)
tree87b2e88ef2be86264bedeb0ecb74c9d89f07f815
parent270e7e96d0c5ac63cdc176c6eb91d30d570537ad (diff)
-rw-r--r--doc/forum/security_risk_presented_by_remote.log__63__.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/security_risk_presented_by_remote.log__63__.mdwn b/doc/forum/security_risk_presented_by_remote.log__63__.mdwn
new file mode 100644
index 000000000..c320c7e30
--- /dev/null
+++ b/doc/forum/security_risk_presented_by_remote.log__63__.mdwn
@@ -0,0 +1,5 @@
+I am curious if remote.log in the repository (or anything in the repository for that matter) gives someone access to the data stored in the special remotes.
+
+If I'm using an encrypted s3 special remote, and someone gets access to the entire repository, will they be able to decrypt things? Or is the gpg stuff stored completely separately and therefore completely unaccessable, even if someone got access to the entire contents of the git repository?
+
+What is the cipher and the cipherkeys stored in git show git-annex:remote.log?