summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-11-07 13:41:21 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-11-07 13:41:21 -0400
commit885611d95b428c09f7605a4629274f58d714172a (patch)
tree70fd67986baaa387eb960a2f76e36e4110e25e5c
parentb38e78a6e5673e995eefbfc2a304f21204922510 (diff)
response
-rw-r--r--doc/special_remotes/rsync/comment_13_368f90773db9522c373168e127a39ae6._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/special_remotes/rsync/comment_13_368f90773db9522c373168e127a39ae6._comment b/doc/special_remotes/rsync/comment_13_368f90773db9522c373168e127a39ae6._comment
new file mode 100644
index 000000000..67e09c092
--- /dev/null
+++ b/doc/special_remotes/rsync/comment_13_368f90773db9522c373168e127a39ae6._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 13"""
+ date="2016-11-07T17:40:15Z"
+ content="""
+@davidriod if you're using a rsyncurl that uses ssh, then yes, the
+transmission goes over a secure connection. If the rsyncurl uses
+the rsync protocol, there would be no encryption.
+
+Of course, encryption=none does not keep the data encrypted at rest,
+so the admin of the rsync server can see it etc.
+"""]]