Added a comment: Understanding encrypted special remote folder structure
authorgaknuyardi@f7280525ccd44eafd8d1485ec087f27532efd2e9 <gaknuyardi@web>
Wed, 22 Mar 2023 19:26:56 +0000 (19:26 +0000)
committeradmin <admin@branchable.com>
Wed, 22 Mar 2023 19:26:56 +0000 (19:26 +0000)
doc/special_remotes/comment_51_1a8a217dc31b0a36dfa9975f72d40b3a._comment [new file with mode: 0644]

diff --git a/doc/special_remotes/comment_51_1a8a217dc31b0a36dfa9975f72d40b3a._comment b/doc/special_remotes/comment_51_1a8a217dc31b0a36dfa9975f72d40b3a._comment
new file mode 100644 (file)
index 0000000..59bb3cf
--- /dev/null
@@ -0,0 +1,18 @@
+[[!comment format=mdwn
+ username="gaknuyardi@f7280525ccd44eafd8d1485ec087f27532efd2e9"
+ nickname="gaknuyardi"
+ avatar="http://cdn.libravatar.org/avatar/2cfaf95a0836c7a00ef3efb16c3315ae"
+ subject="Understanding encrypted special remote folder structure"
+ date="2023-03-22T19:26:55Z"
+ content="""
+@joey While inspecting my special remote (rsync, encryption=hybrid) I noticed that a couple files ended up in the same folder tree, is that normal or is something wrong? Obfuscated tree output below.
+
+```
+├── [   0]  xxx
+│   └── [   0]  yyy
+│       ├── [   0]  GPGHMACSHA512--1234
+│       │   └── [29M]  GPGHMACSHA512--1234
+│       └── [   0]  GPGHMACSHA512--5678
+│           └── [ 2G]  GPGHMACSHA512--5678
+```
+"""]]