aboutsummaryrefslogtreecommitdiff
path: root/doc/backends
diff options
context:
space:
mode:
authorGravatar junk@5e3eeba2290e8a3fcf938d9f93b0dfa2565dc7b1 <junk@web>2016-08-14 17:07:03 +0000
committerGravatar admin <admin@branchable.com>2016-08-14 17:07:03 +0000
commitb44bc9d7b42d82e57456370625ef539ff276fae1 (patch)
treeba461e9c8aed1367d0aba6a545a99df2b605ecbf /doc/backends
parentc73f2b7b892ad2d349eee9b696f19d0c687e4976 (diff)
Added a comment: Howto verify encrypted files
Diffstat (limited to 'doc/backends')
-rw-r--r--doc/backends/comment_18_784b29b086503a2b4913558350526ee1._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/backends/comment_18_784b29b086503a2b4913558350526ee1._comment b/doc/backends/comment_18_784b29b086503a2b4913558350526ee1._comment
new file mode 100644
index 000000000..43c554f7f
--- /dev/null
+++ b/doc/backends/comment_18_784b29b086503a2b4913558350526ee1._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="junk@5e3eeba2290e8a3fcf938d9f93b0dfa2565dc7b1"
+ nickname="junk"
+ subject="Howto verify encrypted files"
+ date="2016-08-14T17:07:03Z"
+ content="""
+Hi,
+
+I'd like to be able verify the consistancy of the files on a rsync remote without having access to the git repository or the gpg-key. This can easily be done with unencrypted files by running \"sha256sum filename\". Is there a way to do the same thing with encrypted files?
+
+Thank you very much!
+"""]]