Getting Askpass for every action even when its not needed

I added ssh to the ssh-agent so I don't have to constantly add the password to the sourcegit but it keeps giving me the askpass prompt for pull, push, fetch and commits.

Even when deleting branches I also get the askpass prompt.
What I find wild with deleting branches is that if you cancel the askpass prompt, the branch gets deleted either way.

This window is launched by ssh not SourceGit:

sourcegit/src/Commands/Command.cs

Lines 167 to 175 in 0a74dd6

    
           // Force using this app as SSH askpass program 
        
           var selfExecFile = Process.GetCurrentProcess().MainModule!.FileName; 
        
           if (!OperatingSystem.IsLinux()) 
        
               start.Environment.Add("DISPLAY", "required"); 
        
           start.Environment.Add("SSH_ASKPASS", selfExecFile); // Can not use parameter here, because it invoked by SSH with `exec` 
        
           start.Environment.Add("SSH_ASKPASS_REQUIRE", "prefer"); 
        
           start.Environment.Add("SOURCEGIT_LAUNCH_AS_ASKPASS", "TRUE");

Make sure you have enable the AddKeysToAgent configuration in ~/.ssh/config

Host *
  AddKeysToAgent yes

Hi, I have same problem, mint, manjaro. All time when I want to do some git actions - always prompt for ssh key password

➜  ~ cat ~/.ssh/config
Host *
  AddKeysToAgent yes

If your private key has a passphrase, each time you use it, SSH will ask for its password. You can use ssh-keygen -p -f <private_key> to reset its password to empty.

I added

Host *
  AddKeysToAgent yes

and the ssh-agent is running on my terminal, however I still receive the AskPass prompt.

I even tried it out with a file creating, deleting, committing and pushing over terminal which worked without any issue.
Then the same approach with sourcegit and I still get the prompt.

Then I added this code below in ~/.ssh/config and attempted the same process again.

Host github.com
  AddKeysToAgent yes
  IdentityFile ~/.ssh/id_work
  BatchMode yes

This time, sourcegit decided not to commit or push and simply gave me a "Permission denied (publickey)." error even though it works on the terminal. Not giving me any prompt anymore because of BatchMode yes.

I would also not take the ssh-keygen -p -f <private_key> approach since you are not keeping your SSH Key secure this way.

If this was an SSH issue then it would have also happened on the Terminal which it didn't.

This may be because the private_key_file is passed into the SSH command every time in the code:

sourcegit/src/Commands/Command.cs

Lines 175 to 179 in 0a74dd6

    
           // If an SSH private key was provided, sets the environment. 
        
           if (!start.Environment.ContainsKey("GIT_SSH_COMMAND") && !string.IsNullOrEmpty(SSHKey)) 
        
               start.Environment.Add("GIT_SSH_COMMAND", $"ssh -i '{SSHKey}'");

Later, I'll check if there is a better way to handle the SSH connection.

I test this on Windows platform that when installing GIT, using external openssh (without using the built-in SSH) does not have such problems.

Makes sure ssh-agent service is running

BTW, on which system do you encounter this problem?

BTW, on which system do you encounter this problem?

I use Linux: Manjaro, Mint, Ubuntu distributions

On Windows 10/11 this problem not exists :)

BTW, on which system do you encounter this problem?

I use Linux: Archlinux & Windows 11.

This happened so far only on Archlinux but I will check Windows later today.

I've test this on Ubuntu. After manually add keys to ssh-agent, it will not ask me for passphrase any more.

eval `ssh-agent -s` # Makes sure `ssh-agent` started
ssh-add <private_key_file> # The `<private_key_file` is the same one with `SSH Private Key` of remote configuration in `SourceGit`

# Then restart `SourceGit` and try to fetch/pull/push/create commit in `SourceGit`

I think I know why.

When I started SourceGit from the terminal session that just runs eval `ssh-agent -s` , this issue does not exists
When I started SourceGit from other terminal sessions that have not ran eval `ssh-agent -s` , this issue appears

Maybe, SSH_AGENT_PID and SSH_AUTH_SOCK are needed by ssh command

I just tried it myself over AppImage on Archlinux and it still happens for me.
I just did a simple pull on my branch and it pops up.

I've no idea how to deal with this. Different users have reported different situations, and sometimes they are exactly opposite. What can be confirmed at present is that this issue behaves differently on different Linux distributions (this issue does not exist on Windows and macOS platforms).

If anyone has a solution to this problem, please feel free to submit a PR.

Is it possible to have SourceGit not do any extra work related to SSH keys (as a new option)?
I use the FIDO SSH key types (ecdsa-sk / ed25519-s). My operating system prompts me to unlock my FIDO key.
Everything works fine when I use the command line. In SourceGit I get the Askpass popup in addition to the operating system popup.

If I ~~uncomment~~ comment these lines it works.
https://github.com/sourcegit-scm/sourcegit/blob/080c446ce0b24edb437dbdddd515402a0a364b0d/src/Commands/Command.cs#L176C13-L184C95

Something else:
While looking through the SourceCode I noticed that credential.helper seems to always be set to manager. Why is that?

https://github.com/sourcegit-scm/sourcegit/blob/080c446ce0b24edb437dbdddd515402a0a364b0d/src/Commands/Command.cs#L193C1-L197C30

Is it possible to have SourceGit not do any extra work related to SSH keys (as a new option)?

SourceGit use these ENV to make sure there's a GUI-based ask-pass tool. It is the common way that used by many clients, such as GitHub Desktop, GitExtensions, VSCode etc.

While looking through the SourceCode I noticed that credential.helper seems to always be set to manager. Why is that?

This setting is only used for account authentication between git and the hosting platform, and is completely unrelated to this issue. The ssh process does not use this setting.
The reason is basically the same as the previous question. SourceGit needs to ensure that there is a GUI-based tool. For the Linux platform, we provide two options: git-credential-manager or git-credential-libsecret

And this issue only exists on Linux platform. I do not know why.

SourceGit use these ENV to make sure there's a GUI-based ask-pass tool. It is the common way that used by many clients, such as GitHub Desktop, GitExtensions, VSCode etc.

Thanks, that makes sense.

For my specific use case, my operating system handles spawning a GUI. If you could add an option that skips the SSH setup, it would be very helpful to me. 🙏
I have tested that disabling these lines would work for my machine.
https://github.com/sourcegit-scm/sourcegit/blob/080c446ce0b24edb437dbdddd515402a0a364b0d/src/Commands/Command.cs#L176C13-L184C95

feat(ux): upstream issues から UX 改善を 6 件採用

feat(ux): upstream issues から UX 改善を 6 件採用 (#17)

@Doodeletion

I have tested that disabling these lines would work for my machine.

@Doodeletion If that fixes this issue for you, you can try to clear the private key in Edit Remote popup.

Navigation Menu

Repository navigation

Getting Askpass for every action even when its not needed #1577

34 remaining items

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development


	// Force using this app as SSH askpass program
	var selfExecFile = Process.GetCurrentProcess().MainModule!.FileName;
	if (!OperatingSystem.IsLinux())
	start.Environment.Add("DISPLAY", "required");
	start.Environment.Add("SSH_ASKPASS", selfExecFile); // Can not use parameter here, because it invoked by SSH with `exec`
	start.Environment.Add("SSH_ASKPASS_REQUIRE", "prefer");
	start.Environment.Add("SOURCEGIT_LAUNCH_AS_ASKPASS", "TRUE");


	// If an SSH private key was provided, sets the environment.
	if (!start.Environment.ContainsKey("GIT_SSH_COMMAND") && !string.IsNullOrEmpty(SSHKey))
	start.Environment.Add("GIT_SSH_COMMAND", $"ssh -i '{SSHKey}'");

Getting Askpass for every action even when its not needed #1577

Description

Activity

love-linger commented on Jul 15, 2025

love-linger commented on Jul 15, 2025

piotr-fraczek commented on Jul 16, 2025

love-linger commented on Jul 17, 2025

Akira-Kuru commented on Jul 18, 2025

love-linger commented on Jul 18, 2025

love-linger commented on Jul 21, 2025

piotr-fraczek commented on Jul 21, 2025

Akira-Kuru commented on Jul 21, 2025

love-linger commented on Jul 21, 2025

love-linger commented on Jul 21, 2025

34 remaining items

Akira-Kuru commented on Aug 14, 2025

love-linger commented on Aug 27, 2025

Doodeletion commented on Feb 7, 2026

love-linger commented on Feb 8, 2026

love-linger commented on Feb 8, 2026

Doodeletion commented on Feb 8, 2026

love-linger commented on Jun 3, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions