require git config to enable

[joeyh]

If I installed this and then cloned some git repository and used git-annex, it would be possible for the repository to have an autoenabled special remote of type remote-getexec. So any git repository I happen to clone could run arbitrary code.

I think this should need a git config be set to enable it. If you wanted that could be set globally, but in normal use it would be set for the git repository you trust.

See also my comment here https://git-annex.branchable.com/todo/compute_special_remote/#comment-b4efb7e9df2bcc55bcb059c51c0c0229

[matrss]

Indeed, that would make it safer.

I also like the proposed idea of a whitelist for autoenabled remotes though. Auto-enabling always felt a bit weird to me. git annex init could instead make it an interactive prompt to the user, similar to what nix does with potentially dangerous configuration options in flakes:

$ nix develop
do you want to allow configuration setting 'extra-substituters' to be set to 'https://cache.garnix.io' (y/N)? y   
do you want to permanently mark this value as trusted (y/N)? y
do you want to allow configuration setting 'extra-trusted-public-keys' to be set to 'cache.garnix.io:CTFPyKSLcx5RMJKfLo5EEPUObbA78b0YQ2DTCJXqr9g=' (y/N)? y
do you want to permanently mark this value as trusted (y/N)? y
$ cat ~/.local/share/nix/trusted-settings.json 
{"extra-substituters":{"https://cache.garnix.io":true,"https://matrss.cachix.org":true},"extra-trusted-public-keys":{"cache.garnix.io:CTFPyKSLcx5RMJKfLo5EEPUObbA78b0YQ2DTCJXqr9g=":true,"matrss.cachix.org-1:02DRX8OkVWrsB8uF2rT736b+ILcVd73qn2rB/n64VQ4=":true}}