> On 01 June 2018 at 01:41 Werner Koch wrote:
>
>
> On Fri, 1 Jun 2018 00:04, koo...@spacekookie.de said:
>
> > ssb> rsa4096 2018-05-30 [SEA]
>
> Remove the S capability from that key. gpg prefers a signing subkey
> over the primary key but that happens to be an encryption key on the
>
> On 31 May 2018 at 21:12 Werner Koch wrote:
>
> You are signing with the second key of the token. This is an encryption
> key and thus not able to sign. If you do a "gpg -card-status" can you
> see an Signature key (In the log "OpenPGP.1")?
Hmmm...this is the output of gpg2 --card-status
Hey there, thanks for the reply :)
> On 31 May 2018 at 19:41 Werner Koch wrote:
>
>
> On Thu, 31 May 2018 16:12, koo...@spacekookie.de said:
>
> > [GNUPG:] FAILURE sign 100663414
> > gpg: signing failed: Invalid ID
>
> $ gpg-error 100663414
> 100663414 = (6, 118) = (GPG_ERR_SOURCE_SCD,
Hey there,
I have a yubikey 4 that contains my GPG key. I can use the `gpg2` tool to sign
messages without problems. But when I try to do the same with git, it fails.
The command that git runs internally is equivalent to this:
echo "This is a stream from git..." | gpg2 --status-fd=2 -bsau
