diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-05-24 13:38:17 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-05-24 13:38:17 -0400 |
| commit | ae22d1c67682f02c0bfcfb8f1a6541209b98173a (patch) | |
| tree | 5791c08ad3bce15c6e7cae4f028d77140bdd6174 | |
| parent | bc46b86f435daddd070cdc341865733d96ae360a (diff) | |
response
| -rw-r--r-- | doc/forum/Malicious_autoenabled_remotes/comment_3_608213f5d0df482b731ae1502cdd87af._comment | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/Malicious_autoenabled_remotes/comment_3_608213f5d0df482b731ae1502cdd87af._comment b/doc/forum/Malicious_autoenabled_remotes/comment_3_608213f5d0df482b731ae1502cdd87af._comment new file mode 100644 index 000000000..702be5fbb --- /dev/null +++ b/doc/forum/Malicious_autoenabled_remotes/comment_3_608213f5d0df482b731ae1502cdd87af._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2017-05-24T17:27:20Z" + content=""" +The server can certainly do filtering or blocking of changes to the +git-annex branch to prevent this kind of abuse. + +Marking a repository as dead will indeed prevent it from being +auto-enabled. It will not cause later synchronisation problems. It seems +like a perhaps too big hammer though. Cloning from such a server, and then +pushing back to it would make your clone be marked as dead on the next +pull! + +And marking dead doesn't prevent malicious changes to preferred +content settings etc. + +Filtering in the `pre-receive` hook should be very doable. See +[[internals]] for the git-annex branch documentation. +"""]] |