aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/External_special_remote_broken__63__/comment_1_904a186a6400506303cad772ac1a6751._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/External_special_remote_broken__63__/comment_1_904a186a6400506303cad772ac1a6751._comment')
-rw-r--r--doc/bugs/External_special_remote_broken__63__/comment_1_904a186a6400506303cad772ac1a6751._comment15
1 files changed, 0 insertions, 15 deletions
diff --git a/doc/bugs/External_special_remote_broken__63__/comment_1_904a186a6400506303cad772ac1a6751._comment b/doc/bugs/External_special_remote_broken__63__/comment_1_904a186a6400506303cad772ac1a6751._comment
deleted file mode 100644
index 7fb3b08e5..000000000
--- a/doc/bugs/External_special_remote_broken__63__/comment_1_904a186a6400506303cad772ac1a6751._comment
+++ /dev/null
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="joey"
- subject="""comment 1"""
- date="2016-04-27T16:23:43Z"
- content="""
-Reproduced this using a directory special remote.
-
-The first checkpresent is because a file can be present on a remote in
-non-chunked form, since a remote can be reconfigured to add chunking.
-So it's nothing to worry about.
-
-The lack of encryption of the key when checking to resume is definitely a
-bug. A bit of a security bug too.
-(I double checked the other operations and they all encrypt keys)
-"""]]