I would find it useful. For example I'm making a utility that gets a passphrase with GPGME and gpg-agent, and would like to copy it into a buffer that lives on after closing the context.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 14 2020
Nov 13 2020
Nov 12 2020
Please ask on a mailing list - this is a bug tracker and somehow expects bug descriptions.
Sorry, I do not understand what kind of bug you are trying to report. it seems that you have a question about some software and you assume this is gpg4win. "invalid pocket" is however not an error any of our software emits.
Note that Kleopatra verifies the currently active card before starting the generation of new keys. This prevents the destruction of keys on the wrong card.
I am trying to solve this problem since one month
BTW, the idea is to fade out support for gpg --card-status and --card-edit. Thus no new features there. New features shall only go into gpg-card.
Fixing --card-status is definitely a good idea. gpg-card shows almost the same information as gpg --card-status except that it shows the correct "Version" and "Serial number". It would probably make sense to unify the code of --card-status and gpg-card's list command.
Thanks for your report, but your excerpt is irrelevant.
Push the change.
Thank you.
Let me describe current situation.
Nov 11 2020
Released with GpgOL 2.4.6 ang gpg4win 3.1.12
This is in 3.1.12
3.1.12 was released on 2020-07-24.
This is a regression of the multi-card, multi-app support in Kleopatra, i.e. T5066. Generating OpenPGP keys fails because the PIV app is active on the card and the code does not switch to the OpenPGP app. (It also does not switch to the correct card if multiple cards are inserted which could result in the destruction of keys on the wrong card.)
I just noticed that gpg --card-status now prints a bogus OpenPGP version number for my Yubikey. And it prints an empty serial number.
# gpg --card-status Reader ...........: 1050:0407:X:0 Application ID ...: FF020001008A7796 Application type .: OpenPGP Version ..........: 77.96 Manufacturer .....: Yubico Serial number ....:
Closing as discussed with @aheinecke
Thanks.
I didn't consider well about the test environment which uses special pinentry program.
I'll fix the line 155.
Nov 10 2020
"Revoke Certification(s)" is available in
- Certifications Overview as context menu option for the user IDs
- Certifications Overview as context menu option for the signatures
- Certificate Details as context menu option for the user IDs
- Certificate Overview (aka key list) as context menu option for keys
- Certificate Overview (aka key list) as menu entry of Certificates menu
This change breaks tests/openpgp/delete-keys.scm:
# cd tests/openpgp # TESTS="delete-keys.scm" make check [...] PASS: tests/openpgp/setup.scm ("/home/ingo/dev/g10/build/gnupg/g10/gpg" --no-permission-warning --always-trust --delete-secret-keys "A0FF4590BB6122EDEF6E3C542D727CC768697734") failed: gpg: can't do this in batch mode without "--yes"