-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Correctly attempt multiple usernames with libgit2 #2584
Conversation
@bors r+ |
📌 Commit d81776b has been approved by |
⌛ Testing commit d81776b with merge 8d21210... |
💔 Test failed - cargo-mac-64 |
@bors: r=brson 897034e |
⌛ Testing commit 897034e with merge c8af5df... |
💔 Test failed - cargo-win-msvc-64 |
This commit corrects the logic for attempting multiple usernames with libgit2. There is a restriction that for each authentication seession you can only authenticate with one ssh username, but we were attempting multiple as part of the same sesssion. Instead restart authentication whenever we try a new username. Closes rust-lang#2399
@bors: r=brson |
📌 Commit 537f718 has been approved by |
Correctly attempt multiple usernames with libgit2 This commit corrects the logic for attempting multiple usernames with libgit2. There is a restriction that for each authentication seession you can only authenticate with one ssh username, but we were attempting multiple as part of the same sesssion. Instead restart authentication whenever we try a new username. Closes #2399
☀️ Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64 |
This commit corrects the logic for attempting multiple usernames with libgit2.
There is a restriction that for each authentication seession you can only
authenticate with one ssh username, but we were attempting multiple as part of
the same sesssion. Instead restart authentication whenever we try a new username.
Closes #2399