From e7bd6b8e6e434f2ef78c31884c4ebfb352c5fff9 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 13 Mar 2024 11:19:04 -0400 Subject: [PATCH] update --- doc/design/balanced_preferred_content.mdwn | 4 +++- doc/design/passthrough_proxy.mdwn | 15 +++++++++++++++ 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/doc/design/balanced_preferred_content.mdwn b/doc/design/balanced_preferred_content.mdwn index f46eac8470..2a84b1273c 100644 --- a/doc/design/balanced_preferred_content.mdwn +++ b/doc/design/balanced_preferred_content.mdwn @@ -140,4 +140,6 @@ would surely have been in vain.) ## see also -[[todo/proving_preferred_content_behavior]] +[[todo/proving_preferred_content_behavior]] +[[todo/passthrough_proxy]] + diff --git a/doc/design/passthrough_proxy.mdwn b/doc/design/passthrough_proxy.mdwn index 16b5dc7f0e..c5c9385168 100644 --- a/doc/design/passthrough_proxy.mdwn +++ b/doc/design/passthrough_proxy.mdwn @@ -107,3 +107,18 @@ content. Eg, analize what files are typically requested, and store another copy of those on the proxy. Perhaps prioritize storing smaller files, where latency tends to swamp transfer speed. +## encryption + +When the proxy is in front of a special remote that uses encryption, where +does the encryption happen? It could either happen on the client before +sending to the proxy, or the proxy could do the encryption since it +communicates with the special remote. For security, doing the encryption on +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. + +(Chunking has the same problem.) -- 2.30.2