Fixed in 2.4.4 and 2.2.43 - see above for affected versions.

Works for the two sample RSA cards. Ticket may eventually be re-opened if we run into problems with ECC cards.

Fixes are already in GnuPG 2.4.4 and can't be easily tested. Thus closing also for gnupg24

I wouldn't mind having the c++ and qt bindings in a separate library released at the same time as gpgme but with a cmake build system. It would simplify a lot in the craft build system as building the same repo with two different build system is not something that craft support very well...

Closing because we believe things are fixed and our test suite confirms that. Feel free to -reopen in case your own file does not import with 2.4.4.

The test file is now part of our test suite and passes.

We meanwhile have a lot of test cases in our test suite and we see no issue. Closing this bug; feel free to re-open if it is not fixed for your case in 2.4.4.

I did a couple of test on the command line which should be sufficient.

For existing files it does now do the same as when encrypting. Folders were already renamed automatically to avoid overwriting. This hasn't been changed.

We need to fix 2.2.42 too. This because we backported the responsible patch.

Move back to vsd33 Backlog because the changes may have to be merged to a (future) vsd33 branch.

And it isn't a second build system for all of gpgme, but only for the C++ binding and the Qt bindings.

@werner This has been discussed by you and Andre and you gave green light as far as I know. It's not needed for private things but for providing Windows builds with MSVC for various KDE projects. This will be maintained by KDE people. Yes, we will make clear that this is a non supported way to build things.

Having a second build system for GPGME is not a good idea. This gives us a headache for maintaining. If you really need this for private things, put this into a contrib directory and make clear that this is a non supported way to build things. And for the Qt bindings I am anyway in favor of removing them from GPGME proper.

In D581#6137, @TobiasFella wrote:

Merged. For some reason i can't close it, so I'll abandon it instead...

Merged. For some reason i can't close it, so I'll abandon it instead...

Ship it!

In Gpg4win-4.3.0-beta571 with GnuPG 2.4.4-beta132

>echo test | gpg --sign --default-key F8D51DE0EE16E9B57009B8DE458612006D8E6F0D
gpg: Warning: not using 'F8D51DE0EE16E9B57009B8DE458612006D8E6F0D' as default key: Key expired
gpg: all values passed to '--default-key' ignored
gpg: no default secret key: Unusable secret key
gpg: signing failed: Unusable secret key

It is already implemented and will soon show up in 2.4.4 -)

Fix lang/python/gpgme.i

In T6481#181779, @gniibe wrote:

Arch Linux: https://gitlab.archlinux.org/archlinux/packaging/packages/gnupg
FreeBSD: https://cgit.freebsd.org/ports/tree/security/gnupg

I don't see the patch is applied. Please wait for GnuPG release 2.4.4.

works in Gpg4win-4.3.0-beta571

Can't comment on the autogen code, but the cpp code looks good

Changes:

• Decouple creating a backup of the (secret) key from deleting the copy of the (secret) key stored on disk.
• Improve the button texts and the messages to make it clearer that the copy stored on the computer's disk can be deleted.
• Don't ask a second time for confirmation if a backup has been created.
  • If the user has created a backup of the secret key and then chosen to delete the copy on disk then don't annoy them with another request for confirmation. Even if they accidentally chose to delete the copy on disk they can restore it with the backup.
  • If the user hasn't created a backup (that we know of) then we keep requesting confirmation.