From 4403791c6c6f94aa58320bd36070132f7c79d76e Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 30 Mar 2021 15:17:05 +0000 Subject: [PATCH] Added a comment: autoenabling external special remotes --- .../comment_4_3ace886382ff165db6f36df8743ca7c1._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/todo/dockerized_external_special_remotes/comment_4_3ace886382ff165db6f36df8743ca7c1._comment diff --git a/doc/todo/dockerized_external_special_remotes/comment_4_3ace886382ff165db6f36df8743ca7c1._comment b/doc/todo/dockerized_external_special_remotes/comment_4_3ace886382ff165db6f36df8743ca7c1._comment new file mode 100644 index 0000000000..3998cb0e15 --- /dev/null +++ b/doc/todo/dockerized_external_special_remotes/comment_4_3ace886382ff165db6f36df8743ca7c1._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="autoenabling external special remotes" + date="2021-03-30T15:17:02Z" + content=""" +\"the minimum needed is a way to add a shell script to PATH with the name of the external special remote program\" -- that would of course be simpler; could specify a relative path within the repo itself. But auto-running an untrusted script fetched along with the repo may be risky. A Docker/Singularity container could be sandboxed; or maybe `chroot` or `bash -r` would suffice? + +"""]]