functionality appears to have been removed
by
# commit 8c219602515ae1dba5bc0da31077852dab61809e when g10/gluecard.c
# was removed. From the latest commit, it seems like appropriate logic
# could be added back in agent/divert-scd.c in the main loop of
# ask_for_card f
with recipients.
Here's an example now of what `gpg -K` outputs for me, minus a couple of
additional subkeys I've generated for other devices.
--
sec# rsa4096/0x6CA6A08DBA640677 2019-03-01 [SC]
2C8160E6AF1166154CDAED266CA6A08DBA6
current setup below:
--
sec rsa4096/0x6CA6A08DBA640677 2019-03-01 [SC]
2C8160E6AF1166154CDAED266CA6A08DBA640677
uid [ultimate] Chip Senkbeil (My mail & pass key)
ssb> rsa4096/0x588B4B090695884C 2019-03-01 [E]
ssb> rsa4096/0x8A6B3DB2C23EB74
or
> secondary key to use.
>
> You can take a peek at the documentation here for more info:
> https://www.gnupg.org/documentation/manuals/gnupg/Specify-a-User-ID.html
> There is also a manual here, with more options if it helps:
> https://gnupg.org/documentation/manpage.html
>
Hey folks, I'm trying to figure out if
a) the gpg option --limit-card-insert-tries is currently functioning (I'm
assuming it is)
b) setting --limit-card-insert-tries=1 does what I expect
My current setup is that I have my passwords stored using the pass tool from
passwordstore.org. Each
