From 885611d95b428c09f7605a4629274f58d714172a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 7 Nov 2016 13:41:21 -0400 Subject: response --- .../comment_13_368f90773db9522c373168e127a39ae6._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/special_remotes/rsync/comment_13_368f90773db9522c373168e127a39ae6._comment (limited to 'doc/special_remotes') 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. +"""]] -- cgit v1.2.3