Skip to content
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

"Bad credentials" error when pulling in gitui, works fine using git pull #2216

Closed
braden-godley opened this issue May 4, 2024 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@braden-godley
Copy link

Describe the bug
When I try to push/pull using gitui, I get a "Bad credentials" error. However, I am able to perform git push and git pull without issues.

To Reproduce
Steps to reproduce the behavior:

  1. Open my git repository
  2. Run gitui
  3. Press f to pull.
  4. See error.

Expected behavior
I expect for it to communicate with my SSH agent to use my credentials and successfully perform the git pull/push.

Screenshots
Pulling in terminal:
image
Pulling in gitui:
image

Context (please complete the following information):

  • Operating system: NixOS + 23.11.3920.25e3d4c0d359
  • Gitui Version: 0.26.1
  • Rust version: 1.77.2

Additional context
I am using 1Password as an SSH agent. However, I don't think that it should matter which specific SSH agent I am using. So I'm not entirely sure why this is occurring.

Additionally, I am definitely using SSH for my remote origin:
image

Thanks for the help!

@braden-godley braden-godley added the bug Something isn't working label May 4, 2024
@remique
Copy link
Contributor

remique commented May 4, 2024

This is possibly a duplicate of #495?

@braden-godley
Copy link
Author

braden-godley commented May 6, 2024

Yeah, this seems to be a problem with libssh2 as someone in that issue pointed out. I use a non-standard ssh-agent and libssh2 doesn't read ~/.ssh/config

This is largely a libssh2 issue (it doesn't parse ~/.ssh/config and is an incomplete ssh client implementation due to this). Until this is fixed (either upstream in libssh2, or by gitui dropping the offending dep), the ostensibly 'correct' workaround is:

Closing as a duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants