make it easier to use curl for unusual url schemes
Use curl when annex.security.allowed-url-schemes includes an url scheme not supported by git-annex internally, as long as annex.security.allowed-ip-addresses is configured to allow using curl. Sponsored-by: Luke Shumaker on Patreon
This commit is contained in:
parent
2fc9a0096f
commit
840bd50390
5 changed files with 37 additions and 4 deletions
|
@ -0,0 +1,21 @@
|
|||
[[!comment format=mdwn
|
||||
username="joey"
|
||||
subject="""comment 1"""
|
||||
date="2022-08-15T15:46:40Z"
|
||||
content="""
|
||||
git-annex can be used with any url scheme that curl supports, but you have to
|
||||
configure it to allow using it. See the documentation
|
||||
of annex.security.allowed-url-schemes in the git-annex man page.
|
||||
|
||||
You will also have to set annex.security.allowed-ip-addresses
|
||||
to "all".
|
||||
|
||||
It seems that even with both settings, git-annex still avoids using curl
|
||||
for unsupported url schemes, unless you also set annex.web-options
|
||||
to some option used by curl. That forces it to use curl. I set it to
|
||||
"--netrc". You will probably need to use that option anyway since I think
|
||||
curl needs configuration in a netrc file to authenticate for sftp.
|
||||
|
||||
(I feel that it's a bug that annex.web-options needs to be set to make it
|
||||
use curl, and I've fixed that in master.)
|
||||
"""]]
|
|
@ -1745,6 +1745,9 @@ Remotes are configured using these settings in `.git/config`.
|
|||
repository, possibly causing it to be copied into your repository
|
||||
and transferred on to other remotes, exposing its content.
|
||||
|
||||
Any url schemes supported by curl can be listed here, but you will
|
||||
also need to configure annex.allowed-ip-addresses to allow using curl.
|
||||
|
||||
Some special remotes support their own domain-specific URL
|
||||
schemes; those are not affected by this configuration setting.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue