Confirmed that this issue is fixed with 2.1.8. I was able to delete the secret
key (stubs) and they were properly recreated.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Sep 29 2015
Sep 29 2015
rhertzog added a comment to T2079: gpg2 --card-status won't create proper stubs for (sub)keys which are known but non-usable.
rhertzog added a comment to T2079: gpg2 --card-status won't create proper stubs for (sub)keys which are known but non-usable.
Debian Unstable is now at 2.1.8-1. I guess this version should have the fix as
well? If yes, I can retry.
Aug 25 2015
Aug 25 2015
rhertzog renamed T2079: gpg2 --card-status won't create proper stubs for (sub)keys which are known but non-usable from [smartcard] gpg2 --card-status won't create proper stubs for subkeys which are known but non-usable to [smartcard] gpg2 --card-status won't create proper stubs for (sub)keys which are known but non-usable.
rhertzog added a comment to T2079: gpg2 --card-status won't create proper stubs for (sub)keys which are known but non-usable.
BTW I had this problem on Debian unstable with version 2.0.28-3:
$ gpg2 --version
gpg (GnuPG) 2.0.28
libgcrypt 1.6.3
[...]