comment
authorJoey Hess <joeyh@joeyh.name>
Mon, 9 Oct 2023 18:47:19 +0000 (14:47 -0400)
committerJoey Hess <joeyh@joeyh.name>
Mon, 9 Oct 2023 18:47:19 +0000 (14:47 -0400)
doc/todo/Allow_remote_sync__42___and_ignore__42___in_git_annex_config/comment_1_7a55c03691a6b6738d1a0e2555cb4cea._comment [new file with mode: 0644]

diff --git a/doc/todo/Allow_remote_sync__42___and_ignore__42___in_git_annex_config/comment_1_7a55c03691a6b6738d1a0e2555cb4cea._comment b/doc/todo/Allow_remote_sync__42___and_ignore__42___in_git_annex_config/comment_1_7a55c03691a6b6738d1a0e2555cb4cea._comment
new file mode 100644 (file)
index 0000000..9be581f
--- /dev/null
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2023-10-09T18:39:21Z"
+ content="""
+We can't put commands in `git-annex config` because cloning
+a git repository and using git(-annex) in it should not
+expose you to executing arbitrary code.
+
+It's not clear to me what kind of liveness check git-annex could do. A ssh
+host is not necessarily pingable.
+
+Configuring ssh to use ConnectTimeout=1 or something like that can help
+with long timeouts.
+"""]]