Skip to content
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

Git submit does not with a password-protected RSA key #721

Closed
slymon99 opened this issue Dec 30, 2022 · 3 comments
Closed

Git submit does not with a password-protected RSA key #721

slymon99 opened this issue Dec 30, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@slymon99
Copy link

Description of the bug

$ git submit
branchless: running command: git fetch origin
Enter passphrase for key MYKEY: ⠁ Running Git command: git fetch origin 
⠒ Running Git command: git fetch origin (2.1s)                                               
branchless: running command: git push --force-with-lease origin branch1 branch2
⠙ Pushing branches (0.0s)                                           ░░░░░░░░░░░░░░░░░░░░ 0/3 
⠙ Pushing branches (3.0s)                                           ░░░░░░░░░░░░░░░░░░░░ 0/3 
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Failed to push branches: branch1, branch2

Submit starts to run before I've typed in my keys password and fails.

If I copy git push --force-with-lease origin branch1 branch2 into my command line (i.e. run the same command through git), everything works fine.

Expected behavior

No response

Actual behavior

No response

Version of rustc

No response

Automated bug report

No response

Version of git-branchless

git-branchless-opts 0.7.0-pre.1

Version of git

git version 2.39.0

@slymon99 slymon99 added the bug Something isn't working label Dec 30, 2022
@arxanas
Copy link
Owner

arxanas commented Dec 31, 2022

Thanks for reporting. This looks similar to #433. Do you think the prompting is happening during git fetch or git push?

In my case, I use ssh-agent and ssh-add -K /path/to/key (on macOS) to unlock the key, and then git sync --pull works for me. Does that workaround work for you?

@slymon99
Copy link
Author

Sorry for the late response - yes that workaround works for me. The prompting is happening during git fetch

@arxanas
Copy link
Owner

arxanas commented Jan 18, 2023

I'll close this issue as a duplicate of #721. I wasn't able to find a good workaround (see the issue description there); if you have any ideas, post them on the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants