From 3388722110458317a4d517b8928e03c8110f4fe4 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 28 Jun 2019 16:36:10 +0000 Subject: [PATCH] Added a comment: dockerized external backends --- .../comment_6_d871bdf09932035acc6260c839f45757._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/external_backends/comment_6_d871bdf09932035acc6260c839f45757._comment diff --git a/doc/todo/external_backends/comment_6_d871bdf09932035acc6260c839f45757._comment b/doc/todo/external_backends/comment_6_d871bdf09932035acc6260c839f45757._comment new file mode 100644 index 0000000000..42c82a5d82 --- /dev/null +++ b/doc/todo/external_backends/comment_6_d871bdf09932035acc6260c839f45757._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="dockerized external backends" + date="2019-06-28T16:36:10Z" + content=""" +Similar to [[todo/dockerized_external_special_remotes]], you could support dockerized external backends. You could run a docker container with [networking disabled](https://docs.docker.com/network/none/) and with file access only to the to-be-annexed file(s), through a [read-only volume](https://docs.docker.com/storage/volumes/#use-a-read-only-volume). You could also require the docker image to be [signed](https://docs.docker.com/engine/security/trust/content_trust/) by someone you trust. Then git-annex repos with external-backend keys could still be self-contained. +"""]]