@@ -191,6 +191,22 @@ network traffic inspection tool such as [Telerik Fiddler][telerik-fiddler]. If
191
191
you are using such tools please consult their documentation for trusting the
192
192
proxy root certificates.
193
193
194
+ ---
195
+
196
+ ## Unsafe Remote URLs
197
+
198
+ If you are using a remote URL that is not considered safe, such as unencrypted
199
+ HTTP (remote URLs that start with ` http:// ` ), host providers may prevent you
200
+ from authenticating with your credentials.
201
+
202
+ In this case, you should consider using a HTTPS (starting with ` https:// ` )
203
+ remote URL to ensure your credentials are transmitted securely.
204
+
205
+ If you accept the risks associated with using an unsafe remote URL, you can
206
+ configure GCM to allow the use of unsafe remote URLS by setting the environment
207
+ variable [ ` GCM_ALLOW_UNSAFE_REMOTES ` ] [ unsafe-envar ] , or by using the Git
208
+ configuration option [ ` credential.allowUnsafeRemotes ` ] [ unsafe-config ] to ` true ` .
209
+
194
210
[ environment ] : environment.md
195
211
[ configuration ] : configuration.md
196
212
[ git-http-proxy ] : https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpproxy
@@ -212,3 +228,5 @@ proxy root certificates.
212
228
[ git-ssl-no-verify ] : https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables#_networking
213
229
[ git-http-ssl-verify ] : https://git-scm.com/docs/git-config#Documentation/git-config.txt-httpsslVerify
214
230
[ telerik-fiddler ] : https://www.telerik.com/fiddler
231
+ [ unsafe-envar ] : environment.md#gcm_allow_unsafe_remotes
232
+ [ unsafe-config ] : configuration.md#credentialallowunsaferemotes
0 commit comments