-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
git-fetch-with-cli doesn't work well with custom registries #6241
Comments
Hm interesting! Can you try running with |
That's down on the last line:
|
Er right, sorry! Since that doesn't work, can the user be specified in the url when configuring? |
Nope, allowing that is the proposed fix :P
|
Sorry I'm definitely a bit slow today... Seems like a solid use case to me to relax the restriction! |
sfackler
added a commit
to sfackler/cargo
that referenced
this issue
Oct 31, 2018
We want to forbid secrets since they'll commonly end up checked into source control, but usernames are fine (and are commonly going to be `git`). Closes rust-lang#6241
bors
added a commit
that referenced
this issue
Nov 1, 2018
Allow usernames in alt registry URLs We want to forbid secrets since they'll commonly end up checked into source control, but usernames are fine (and are commonly going to be `git`). Closes #6241 r? @alexcrichton
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The git repository URLs for custom registries are currently forbidden from containing credentials. Unfortunately, that interacts poorly with the
git-fetch-with-cli
option since command-line git will default to using your username as the username when authenticating. However, a common configuration (e.g. with Github) is to use a single user namedgit
for all users, so you end up with an error:Note how the Permission denied message tried
sfackler@my-git-server
rather thangit@my-git-server
which would have worked.It seems like we should relax the restriction on credentials in custom registry configurations to only forbid passwords and not usernames.
The text was updated successfully, but these errors were encountered: