gpg crashes the solokey v2, firmware 0.128.241 about solo2-cli HOT 1 CLOSED

If anyone stumbles on this issue (which I'm closing), the problem does seem to be a firmware issue. As reported here, the issue is likely caused by some missing abort handling in the code.

GnuPG itself it also probably to blame, as scdaemon sees the solokey v2 as an OpenPGP smartcard, which it is not.

The way to "fix" this issue (a proper fix would probably be a firmware one...) is to use the reader-port argument in scdaemon not to match the solokey:

1. Plug both your solokey v2 and your OpenPGP smartcard
2. Run the following command, to get a list of the tokens scdaemon sees: $ echo scd getinfo reader_list | gpg-connect-agent --decode | awk '/^D/ {print $2}'
3. Identify your OpenPGP smartcard. For example, my Nitrokey Smart is listed as 20A0:4211:FSIJ-1.2.15-43211613:0
4. Create a file in ~/.gnupg/scdaemon.conf that includes the following line reader-port $YOUR_TOKEN_ID. For example, in my case it is: reader-port 20A0:4211:FSIJ-1.2.15-43211613:0
5. Reload scdaemon: $ gpgconf --reload scdaemon

Voilàààà.

from solo2-cli.