From 7d407516c4779bc644a5b91e7de8ff23e4dc3ff7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 13 Mar 2024 11:21:05 -0400 Subject: [PATCH] update --- doc/design/passthrough_proxy.mdwn | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/design/passthrough_proxy.mdwn b/doc/design/passthrough_proxy.mdwn index c5c9385168..91830f41ce 100644 --- a/doc/design/passthrough_proxy.mdwn +++ b/doc/design/passthrough_proxy.mdwn @@ -117,8 +117,11 @@ the client seems like the best choice by far. But, git-annex's git remotes don't currently ever do encryption. And special remotes don't communicate via the P2P protocol with a git remote. -So none of git-annex existing remote implementations would be able to handle -this case. So something will need to be changed in the remote -implementation to handle this case. +So none of git-annex's existing remote implementations would be able to handle +this case. Something will need to be changed in the remote +implementation for this. (Chunking has the same problem.) + +There's potentially a layering problem here, because exactly how encryption +(or chunking) works can vary depending on the type of special remote.