From 71206a8603698fd542b8b44e9292aee72586c820 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 27 Jan 2025 10:25:55 -0400 Subject: [PATCH] update comment --- ...omment_6_f1760976e65ae16d4d79f004ac924e55._comment | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/doc/todo/compute_special_remote/comment_6_f1760976e65ae16d4d79f004ac924e55._comment b/doc/todo/compute_special_remote/comment_6_f1760976e65ae16d4d79f004ac924e55._comment index 69d2f42283..c88156c5d1 100644 --- a/doc/todo/compute_special_remote/comment_6_f1760976e65ae16d4d79f004ac924e55._comment +++ b/doc/todo/compute_special_remote/comment_6_f1760976e65ae16d4d79f004ac924e55._comment @@ -3,11 +3,14 @@ subject="""comment 6""" date="2024-04-30T19:53:43Z" content=""" -On trust, it seems to me that if someone chooses to enable a particular -special remote, they are choosing to trust whatever kind of computations it -supports. +On trust, it seems to me that if someone chooses to install a +particular special remote, they are choosing to trust whatever kind of +computations it supports. Eg a special remote could choose to always run a computation inside a particular container system and then if you trust that container system is -secure, you can choose to use it. +secure, you can choose to install it. + +Note that enabling the special remote is not necessary, because a +repository can be set to autoenable a special remote. """]]