From: Clemens Haffner <c.f.haffner@gmail.com>
To: git@vger.kernel.org
Subject: Bug in git-gui
Date: Sun, 29 Sep 2024 19:05:32 +0200 [thread overview]
Message-ID: <69e3564e-3314-4a6e-b489-11a96022e08c@gmail.com> (raw)
Hi,
I think I found a bug in git-gui on Windows (Windows 10 64 bit)
git-gui Version 0.21.GITGUI
git Version: 2.44.0.windows.1
To reproduce: (I have not tested it with rsa keys)
- Create an ed25519 key with a passphrase (--> .ssh/id_ed25519).
Help->Show ssh key detects that key perfectly and shows the Public key
to copy
- Push something to a repository:
--> it will fail.
> Pushing to xxx.xxx:clemens/test_repo.git
> CreateProcessW failed error:193
> ssh_askpass: posix_spawnp: Unknown error
> git@git.xxx.xxx: Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
- When using a key without a passphrase, it works perfectly well.
- When using ssh-agent with a key that uses a passphrase, it also works
well.
> Pushing to git.xxx.xxx:clemens/test_repo.git
> To git.xxx.xxx:clemens/test_repo.git
> = [up to date] rev1 -> rev1
> updating local tracking ref 'refs/remotes/origin/rev1'
> Everything up-to-date
this bug must be in git gui, as it works perfectly fine via git bash.
"git push" spawns a new window, which asks for the passphrase. After
entering the phrase git works as intended.
It seems to me that the git gui cant spawn that window where it asks for
the key.
If that helps:
I'm using Microsofts OpenSSH implementation:
> $ ssh -V
> OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
Greetings,
Clemens Haffner
next reply other threads:[~2024-09-29 17:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 17:05 Clemens Haffner [this message]
2024-09-29 17:43 ` Bug in git-gui Johannes Schindelin
2024-09-29 17:44 ` Johannes Schindelin
2024-09-29 18:35 ` Clemens Haffner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69e3564e-3314-4a6e-b489-11a96022e08c@gmail.com \
--to=c.f.haffner@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).