Repository navigation
support agent-less ssh operation #1023
Description
Please guide me to a way to provide additional information…
Yes, I use SSH URLs for git.
No, they are not password protected.
If though starting SSH-Agent and adding the key, the error becomes:
Error: ssh: handshake failed: knownhosts: key mismatch
Regular git operations against the remote work.
Activity
patricioantoniotoledo commentedon Sep 25, 2023
cd ~/.ssh
ssh-add ~/.ssh/id_rsa
might help
NobbZ commentedon Nov 5, 2023
To be honest, I do not even (want to) use SSH-agent.
I want the configured SSH-config to be respected and the command to just work.
I stoped using
git-bugbecause of this a couple of days after posting this issue without a reply.octvs commentedon Dec 21, 2023
Might be related, I had a similar issues prompting an handshake fail, which was fixed by building from source.
dllud commentedon Jan 24, 2024
I was facing the exact same error in the title. Besides starting a SSH Agent
eval "$(ssh-agent -s)"and adding the keyssh-add ~/.ssh/mykey, I had to use a full URL (ssh://[email protected]:22/path/to/project.git) in the git remote. Only this gotgit bug push/pullworking. This workaround was reported by @Subfortytwo at #572.It seems like the SSH Agent does not read my
~/.ssh/config?Anyway, I am on the same page as @NobbZ: I would rather avoid using a SSH Agent. Is that possible? It wasn't needed last time I used git-bug (a couple years ago).
github-actions commentedon Jul 23, 2024
This bot triages untriaged issues and PRs according to the following rules:
lifecycle/stalelabel is appliedlifecycle/stalewas applied, the issue is closedTo remove the stale status, you can:
lifecycle/stalelabelstackengineer commentedon Nov 2, 2024
Not stale. Also looking for an agentless solution, preferably respecting
~/.ssh/config.[-]Error: error creating SSH agent: "SSH agent requested but SSH_AUTH_SOCK not-specified" on `git bug push`[/-][+]support agent-less ssh operation[/+]sudoforge commentedon May 13, 2025
catching up with some (old) comments here. i'm sorry there hasn't been a response on this issue.
@NobbZ:
hmm, this shouldn't be happening. if you can ssh to the host (or
git pushto it), git-bug should work as well (with a few caveats).i've introduced a few fixes for ssh-related operations (namely: resolving the URI), but git-bug still doesn't read your
~/.ssh/config(which we need to do manually because go-git doesn't), so if you have custom ports or configuration in there, git-bug won't be able to pick it up.if you (or someone else) is still able to reproduce this (with
[email protected]or greater), please let me know.@dllud:
this shouldn't be the case anymore. i technically have fully qualified SSH URIs like this because i use
url.*.insteadOfremapping, but i've tested without those using git's shorthand<user>@<hosname>:foo/bar.gitand that works without issue. as mentioned above, however, custom configuration in~/.ssh/configisn't parsed.yes, i think that git-bug should "just work" like git does. getting to this point is a focus for me in the near term.
dllud commentedon May 13, 2025
Thanks for reviving this @sudoforge !
git's shorthand (scp like syntax) won't work for me (until
~/.ssh/configgets parsed) as I need to set a custom port. The scp like syntax does not allow setting a custom port number.Current status for me on version
0.9.0is:git bug pullor push without starting an agent, I get:~/.ssh/configis not honored.Hope you can find the time to fix both and get git-bug to seamlessly work just like git. ;)
sudoforge commentedon May 13, 2025
yeah, this is something i know about -- parsing custom ssh config is on my radar.
in the meantime, if your only need is to specify a custom port, using the full RFC-3986-compliant URI would work for you:
yep - this is on my radar as well.
generally speaking, the way git-bug is currently written makes a lot of assumptions about your git configuration, your ssh configuration, and the types of remotes you're interacting with. these are the core issues i want to solve in the near term, as they are silly, and outright blocking people.