mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

response

Browse source
This commit is contained in:
Joey Hess 2017-05-24 13:38:17 -04:00
parent d6c0b25147
commit ec8515d37c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/forum/Malicious_autoenabled_remotes/comment_3_608213f5d0df482b731ae1502cdd87af._comment Normal file
View file

@ -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.
"""]]