mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

update

Browse source
This commit is contained in:
Joey Hess 2024-03-13 11:19:04 -04:00
parent ff05c00924
commit e7bd6b8e6e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 18 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/design/balanced_preferred_content.mdwn
View file

@ -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]]

15
doc/design/passthrough_proxy.mdwn
View file

@ -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.)