git-remote-gcrypt incompatible with ssh user.signingkey?

[Sean Whitton]

Hello,

On Mon 17 Jul 2023 at 03:29pm +10, Wesley Moore wrote:

> Hello,
>
> Thanks for you efforts maintaining git-remote-gcrypt. Wanted to run an issue I ran into past you.
>
> From git 2.34 it became possible to sign commits with an SSH key[1]. I am
> using this but it seems that it is not compatible with git-remote-gcrypt. You
> can see my git config here:
>
> https://github.com/wezm/dotfiles/blob/6f5a8fc22636065122cc3022503aa43f703ee016/config/git/config
>
> The user.signingkey, gpg.format, and commit.gpgsign setting are relevant. When
> I try to push my repo with this configuration I see:
>
> gcrypt: Encrypting to: --throw-keyids --default-recipient-self
> gcrypt: Requesting manifest signature
> usage: gpg [options] --sign --encrypt [filename]
> error: failed to push some refs to 'gcrypt::rsync://git@myhost:private.git'
>
> (where my real host is replaced with myhost)
>
> If I switch my git config back to an earlier version[2] that signs with gpg, then the error does not happen.
>
> Environment info:
>
> OS: Arch Linux
> Git version: 2.41.0
> git-remote-gcrypt version: 1.5
>
> Based on the error and format of my user.signingkey it's possible that this is
> another instance of the issue handling spaces in user.signingkey that was
> reported previously[3], although I don't think it's possible to format the ssh
> key without spaces (I think the leading "ssh-rsa " is required).

Yes, it sounds like a bug.  It shouldn't matter at all whether or not
you are SSH-signing any commits.

-- 
Sean Whitton