Thu, Mar 7
Changes backported to 2.2
Wed, Feb 27
We also need to fix for encryption and signature in CSR.
Tue, Feb 26
Builds fine now with GCC 9. Thanks for looking into this so quickly.
Fixed in master, by removing use of compound literals. Compound literals are not portable feature (even for C99 code), so, it's good to avoid when we can.
Still dns.c uses C99 features of struct initializer with name.
Mon, Feb 25
Fixed in master.
Nov 5 2018
No more complaints thus time to close.
Nov 29 2017
If more fine-grained control is needed with suspend-to-ram, we need to write kernel driver for USB access.
I learned suspend-to-ram functionality. Currently, for Linux, if we have USB driver in kernel, there are methods to handle suspend-to-ram and resume events. For user space driver by libusb, there is nothing and it should all work well by reseting after resume.
Nov 14 2017
Tested with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.
Nov 13 2017
Jochen could you please test this on one of our test VM's again and resolve this then?
Oct 26 2017
Oct 24 2017
I am closing this bug report, as I can't get feedback to fix something.
Oct 20 2017
gniibe: Can you check the status?
2.0 reached eol in 2 months so need to check it. For 1.4 I assume it has been fixed ;-)
Aug 8 2017
Aug 7 2017
I also have to add that, if this really has been resolved, it only covers up the case if the missing subkey(s) is/are on the smartcard(s), it does not solve the problem when none of the missing signing subkeys are in smartcards (as in, all on different computers). And it's clear that for version 2.1.22, it fails to get the available subkey on the disk for this case.
@gniibe: I've tested 2.1.22 (from Debian experimental) and, while gpg --sign works, other programs (eg: git tag -s) still prompt to insert the card of the first signing subkey, despite the card with the second signing subkey being present.
Is that expected?
Aug 1 2017
It's there in GnuPG 2.1 for a while, and bugs introduced by change were fixed.
So, I'm closing this bug.
@fogine , I'm afraid your comment is related to this bug particular report of T1983: gpg2 prefers missing secret key to available key on card.
And your problem cannot be replicated by my environment with 2.1.22.
If you still have the issue with 2.1.22, please open new ticket.
gpg (GnuPG) 2.1.21
Jun 30 2017
I added a new task status "Testing".
Jun 29 2017
On Wed, 28 Jun 2017 15:47, email@example.com said:
What tests do you want to be done?
Jun 28 2017
What tests do you want to be done?
Given that we have no TESTING status, the only way I can handle this is by keeping the ticket open and add the TESTING flag. Closing a bug which has not been tested is a bad idea.
Jun 27 2017
@werner An open ticket should mean there is something that can be acted upon. Unless you are saying that we should actively look for regressions or should actively do more testing, this ticket should be closed now. There is plenty of peripheral information that will remind us of this ticket in case more issues resurface related to this change.
Jun 26 2017
Jun 23 2017
I have tested this and it appears to fix the leak of gpg-agent processes in virt-builder, thanks.
I commited a change which should fix this on Linux
This is such a large change that I feel uneasy to close the bug before we know that there are no regressions. This Means we need to wait whether the next release will break.
Jun 5 2017
May 23 2017
I applied another approach: rGfbb2259d22e6: g10: Fix default-key selection for signing, possibly by card.
May 19 2017
Sorry, my fix was not good. Re-opening.
May 16 2017
Fixed in 2.1.21.
May 8 2017
This seems to work just fine on our archlinux box with the nsswitch configuration above.
Justus, will you please so kind and take care of this.
Apr 27 2017
Sorry, I was wrong. The patch also works for signing to key.
The impact is gpg frontend always asks gpg-agent for card key.
It involves invoking scdaemon and accessing to USB.
Apr 24 2017
Will be released with 3.0
Apr 4 2017
I don't have one of these systems handy to test with, but if the fix in dee026d7 does what it says it does, this sounds like it's probably OK to close in my book. if there are more problems, i'm sure we can re-open it.