-
Notifications
You must be signed in to change notification settings - Fork 420
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
ssh_dispatch_run_fatal when git.subprocess=true #5968
Comments
Thanks for the report! I see SSH is connecting to a local network address on an unusual port; would you be able to share anything relevant from your repository remote configuration, your Git configuration, and your SSH configuration? It’d also be useful to know your Git version and if a direct |
Hi! Thanks for opening this issue. Also, could you paste the output of |
The IP address and portit's a remote that is hosted by the company I work for, and it so happens that they chose this IP and port My git config
My SSH config
Git version
Does
|
Could you show the output of these commands?
The
It seems like |
It looks like Fedora 41 deliberately disabled support for insecure SHA‐1 signatures:
That is why SSH to the Git server doesn’t work. If your server still requires that deprecated algorithm, it looks like the cryptography policies will need adjusting with |
Also, it looks like your SSH configuration syntax is wrong; I believe |
Description
After updating jj to 0.27, I started having issues with fetching updates from my git remote:
Setting
git.subprocess = false
in my config resolves the issue, I can fetch without issues.Expected Behavior
jj git fetch
should continue to work with default jj settings.Actual Behavior
fetch fails with
git.subprocess = true
Specifications
The text was updated successfully, but these errors were encountered: