Help with SSH and GPG subkey for authentication

[swedebugia]

On 2019-02-23 12:43, Chris Coutinho wrote:
> On Feb-22-19, swedebugia wrote:
snip

>>
> 
>> enable-ssh-support
> 
>> 7338C1836152D95BBCEFF33F45C49516CC810826
> 
>> _______________________________________________
>> Gnupg-users mailing list
>> Gnupg-users at gnupg.org
>> http://lists.gnupg.org/mailman/listinfo/gnupg-users
> 
> What is the key that you in include in the .gnupg/sshcontrol file? On my
> system, it's the authentication subkey's 'keygrip'. I'm not exactly sure
> what the difference is between that and a fingerprint, but you can
> determine what it is using:
> 
> $ gpg --list-secret-keys --with-keygrip
> 
> Then make sure the keygrip in 'sshcontrol' matches the keygrip of your
> authentication subkey.
> 
> Cheers,
> Chris

I think I did it correctly. Here is the output of the grip:
$ gpg2 --with-keygrip -k swedebugia
pub   ed25519 2019-02-22 [SC] [expires: 2021-02-21]
      7A2163653A22E7F610FA6B55CFCD435B280B6CD2
      Keygrip = E1A8AB878329A205F4F3A5BD899EAD95996DD344
uid           [ultimate] swedebugia <swedebugia at riseup.net>
sub   cv25519 2019-02-22 [E] [expires: 2021-02-21]
      Keygrip = B0CA7175D7173FC906264F1A55DDE766A572ECFB
sub   ed25519 2019-02-22 [A] [expires: 2021-02-21]
      Keygrip = 7338C1836152D95BBCEFF33F45C49516CC810826

My problem is that neither gpg-agent nor ssh-add gives me debug output
so I can pinpoint the error.

I resorted to creating a separate ssh-key with ssh-keygen instead as it
seems to be a hassle to keep it in gpg and use it from there.

-- 
Cheers Swedebugia

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20190223/8700a488/attachment.sig>