- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mar 30 2019
@vsrinu26f No worries, looks like we are on the same page :)
Sorry i think i blabbered without understanding context.
I wish gnupg natively supports creating backup cards. To be able to import
private key material to do another keyto card. And every time it moves that
to card and removes from gnupg.
For exactly same key material on tokens. Just before writing first token
backup .gnupg folder or export all key info. Do key to card. Delete .gnupg
folder and restore from backup and keytocard second token.
Mar 29 2019
Both tokens should have same material.
On the other hand if we want to track which token is used by having multiple unexpired signing subkeys and each token have its own subkey is a possible usecase where multiple admins have the tokens.
I think if we have to update one token then we have to update backup token as well if moved to new subkey.
@vsrinu26f Yes I'm using subkeys with YubiKey.
Sorry, ignore my comment if there is something with subkeys and you are
already using latest gnupg.
This is already implemented by yutaka.
Sorry for jumping in out of the blue but the idea of automatically selecting the available signing key sounds also very appealing to me.
With the downstream report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925952 I resolve this here.
Thanks for the report. This was fixed with: https://cgit.kde.org/libkleo.git/commit/?id=8a94ac0835f0cff8908943d2a630a003a3429220 which I backported to Applications 18.12 which is the current stable release. But debian needs to add this patch. I'll report a debian bug and link it here.
Mar 28 2019
Good that it works again for you.
I don't anymore think that it makes sense to fix it. Further there is no cache for PINs; that is entirely up to the card.
This was most likely a (chipcard) hardware issue. It went away after polishing the contact pads for a bit. Possibly my laptop reader applies more force...
No more reports about this in a while.
Fixed with 3.1.7
False positives happen from time to time with various Anti Virus Software. We have it as a FAQ in the wiki:
https://wiki.gnupg.org/Gpg4win/AntiVirusSoftware
Thanks so much your helps.
With new version 3.1.6, I can generate key on Kleopatra tool and use key stored in smartcard.
The same chipcard works still fine in a different (type of) reader / machine.
Mar 27 2019
Thanks people, thanks aheinecke, for your support.
3.1.6 is released.
3.1.6 is released. Please test again and reopen this issue if you still have problems.
Thanks!
3.1.6 is released
3.1.6 is released.
3.1.6 is released.
3.1.6 is released.
3.1.6 is released.
gpg4win 3.1.6 is released which contains this fix.
3.1.6 is released please use that one.
3.1.6 is released
Sorry, this did not make it into 3.1.6. But I'll definitely see about it for the next release. If it is an institutional / corporate issue you could also contract us through www.gnupg.com