.ssh/config file is ignored, leading to unknown remotes when using aliases

[stfufane]

Hi there,

First, thanks for this great tool I only discovered yesterday, it works very well, really like it so far!

I noticed a small issue while working on a private repository I host on my own server. I have an alias for the ip in my ~/.ssh/config to avoid typing the user+ip every time I need to connect to it. And so my repository uses this alias for the remote url, but gitfourchette seems to ignore it cause it gives me this error when I try to fetch/pull/push

Couldn’t fetch remote: origin — Git error. failed to resolve address for my-host: Name or service not known

Is that something that could be easily solved?

Thanks a lot, cheers :)

[jorio]

Thank you for giving GitFourchette a try!

GitFourchette currently uses libssh2 instead of OpenSSH, so it isn't aware of ~/.ssh/config (OpenSSH configuration file).

I understand that it's a recurring pain point for people with an "off the beaten path" configuration for authentifying with remotes (e.g. #8, #34, #53).

In a future release, I plan to have remote operations go through git itself (instead of libgit2) so that use cases like yours will "just work" with your existing config.

In the meantime, I can suggest changing your remote URL, or maybe give your server a custom hostname in /etc/hosts.

[stfufane]

Ah yes, makes sense, thanks for the fast answer :) No problems for the workaround, it's well enough for my case !

I checked previous issues but didn't realize they were talking about the same problem, sorry for the duplicate. You can close this one as duplicate if it's easier for you to track issues.

[Eonfge]

This is one of those restrictions that really limits the application's corporate use. It would be cool if you could change the backend from libgit2 to git so that these kinds of issues are resolved.

[jorio]

Yup, I'm making this a high priority item, seeing that this is a stumbling block in many people's workflows. I've been generally happy with libgit2 for manipulating git objects without the overhead of shelling out to git itself, so it's got its use for offline tasks. But when it comes to talking to remotes, I believe it'd be more pragmatic to drive vanilla git instead.

[jorio]

Hey @stfufane @Eonfge! GitFourchette v1.5.0 now uses git for remote operations, so your OpenSSH config should apply seamlessly.