[NBug] SSH key file could not be found

[oleopold]

Environment

• Git Extensions 4.0.1.15887
• Build f2567de
• Git 2.38.1.windows.1
• Microsoft Windows NT 10.0.19045.0
• .NET 6.0.12
• DPI 96dpi (no scaling)

Issue description

''

GitUI.NBugReports.UserExternalOperationException: SSH key file could not be found
 ---> System.IO.FileNotFoundException: SSH key file could not be found
   --- End of inner exception stack trace ---
   at GitUI.Infrastructure.PuttyHelpers.ThrowIfFileNotFound(String filePath, String errorMessage, String heading)
   at GitUI.Infrastructure.PuttyHelpers.StartPageantIfConfigured(Func`1 sshKeyFileLoader)
   at GitUI.CommandsDialogs.FormPush.StartPageant(String remote)
   at GitUI.CommandsDialogs.FormPush.PushChanges(IWin32Window owner)
   at GitUI.CommandsDialogs.FormPush.PushClick(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam)

I just tried to push to remote origin.
Pull work just fine.
I use key stored in putty session which I use for accessing remote repository.
So I do not have private key in remote repository configuration.

Steps to reproduce

Try to push into remote configured without explicit ssh key(using putty).

Did this work in previous version of GitExtensions?

Yes

Diagnostics

No response

[duplicates-detector-bot]

Potential duplicates:

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

[vbjay]

So fix your remote config to the correct key file path.

[SymbioticKilla]

Same problem

[RussKie]

Please remove the invalid key reference from your config.

[SymbioticKilla]

@RussKie there is no key. I have two remotes: One is DMZ with public key and one company inside without any key. If I switch to OpenSSH company remote works but I need both to work. It was working in 3.5.4 and the author of this issue said that it worked in 4.0 too.

[oleopold]

I use paegant to manage keys and saved session in putty which tells the key which will be used. So if I have one server from which I clone repositories I do not have to fill key for each of them. It works for command line git and in all previous versions of GitExtensions. It stopped working in latest version.

[SymbioticKilla]

@RussKie @vbjay It is a bug. Just installed V4 and it works. In 4.0.1 doesn't work. In 3.5.4 was also working.

[RussKie]

Does this version fix he issue?
https://ci.appveyor.com/project/gitextensions/gitextensions/builds/45710122/artifacts

[SymbioticKilla]

Works! Thanks!

[oleopold]

Yes, the build works as expected. Thank you.

[gerhardol]

#10545 (comment)

If a key is configured but not available, should the used be informed with a popup or this be ignored?

[oleopold]

#10545 (comment)

If a key is configured but not available, should the used be informed with a popup or this be ignored?

I think that if key is configured than user should be informed when key is missing.

[RussKie]

Please try the latest version: https://ci.appveyor.com/project/gitextensions/gitextensions/builds/45814904/artifacts

[psivanov]

Exact same issue on

• Git Extensions 4.0.2.15986
• Build b063d32
• Git 2.38.1.windows.1
• Microsoft Windows NT 10.0.17763.0
• .NET 6.0.12
• DPI 96dpi (no scaling)
• Microsoft.WindowsDesktop.App Versions

[CorneliusDaniell]

Switch ssh client to OpenSSH instead of PuTTY

[psivanov]

I use pageant like oleopold and it used to work with PuTTY, though...

[mstv]

Exact same issue on

* Git Extensions 4.0.2.15986

Yes, you are right because

https://ci.appveyor.com/project/gitextensions/gitextensions/builds/45814904/artifacts

is the build 15986 right before the integration of the fix.

You could use https://ci.appveyor.com/project/gitextensions/gitextensions/builds/45842693/artifacts.

[psivanov]

Exact same issue on

* Git Extensions 4.0.2.15986

Yes, you are right because

https://ci.appveyor.com/project/gitextensions/gitextensions/builds/45814904/artifacts

is the build 15986 right before the integration of the fix.

You could use https://ci.appveyor.com/project/gitextensions/gitextensions/builds/45842693/artifacts.

Ah, thank you. It works now.