Page MenuHome GnuPG
Feed Advanced Search

Jan 19 2021

werner triaged T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application as Low priority.

Sure that TB uses GPGME - they claimed they won't use it due to license incompatibility (LGPL). I assumed they use gpgme-json via naticve messaging. Regarding the error - I have no idea.

Jan 19 2021, 4:45 PM · gpgme, MacOS, Bug Report

Jan 12 2021

aheinecke closed T4116: Kleopatra: Hang on posix with GPGME_DEBUG=9 as Resolved.

Long since resolved

Jan 12 2021, 12:13 PM · kleopatra, gpgme

Jan 11 2021

aheinecke closed T5225: Release GPGME 1.15.1 as Resolved.
Jan 11 2021, 10:08 AM · Release Info, gpgme
aheinecke closed T5131: Release GPGME 1.15.0 as Resolved.
Jan 11 2021, 10:08 AM · gpgme, Release Info

Jan 8 2021

werner updated the task description for T5131: Release GPGME 1.15.0.
Jan 8 2021, 5:15 PM · gpgme, Release Info
werner created T5225: Release GPGME 1.15.1.
Jan 8 2021, 4:39 PM · Release Info, gpgme

Jan 5 2021

ikloecker closed T3580: GPGME: Keylist mode sigs combined with secret does not work (anymore?) as Resolved.
Jan 5 2021, 5:54 PM · gpgme
ikloecker claimed T3580: GPGME: Keylist mode sigs combined with secret does not work (anymore?).

Taking since I ran into this problem while working on T5174. In Kleopatra, if one opens the certificate details of one's own keys (i.e. secret key is available), then the tags vanish from the key list.

Jan 5 2021, 5:08 PM · gpgme
werner added a comment to T3505: Port GPGME's Python bindings to Windows.

The C++, CL, Javascript and QT Bindings are all written by hand.

Jan 5 2021, 4:06 PM · Feature Request, gpgme, Python
bernhard added a comment to T3505: Port GPGME's Python bindings to Windows.

Hi Werner,

we do it for the other bindings as well.

can you elaborate?

Jan 5 2021, 3:01 PM · Feature Request, gpgme, Python
werner lowered the priority of T3505: Port GPGME's Python bindings to Windows from High to Normal.

Given all the resources we had put on this Python bindings I'd suggest to bite the bullet and replace Swig by handcrafted bindings. More work but we do it for the other bindings as well.

Jan 5 2021, 10:59 AM · Feature Request, gpgme, Python
werner triaged T4883: gpgme X.509 certificates have unknown validity in offline mode unless `disable-crl-checks` is set as Low priority.
Jan 5 2021, 9:31 AM · Not A Bug, S/MIME, gpgme

Dec 12 2020

martinralbrecht closed T4800: python-gpgme signature revokation assertion error: `gpg->cmd.code' failed as Resolved.

You're right. Thank you.

Dec 12 2020, 8:28 PM · gpgme, Bug Report

Dec 3 2020

gniibe claimed T5149: Incorrect error handling in export_key_minimal().

Thanks. Fixed in rM7a4fe82a017b: python: Fix key_export*..

Dec 3 2020, 3:40 AM · Python, gpgme, Bug Report

Dec 1 2020

gniibe closed T5151: GPGME++ : bad passphrase problems as Resolved.
Dec 1 2020, 5:34 AM · segv, gpgme, Bug Report

Nov 26 2020

gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

For ctx->exportPublicKeys returning 0 even when a failure, (with fix of gpg) error handling should be done differently.

Nov 26 2020, 2:22 AM · segv, gpgme, Bug Report

Nov 25 2020

nmset added a comment to T5151: GPGME++ : bad passphrase problems.

Well, I fixed my loopback passphrase provider and the application no longer crashes with a bad passphrase.

Nov 25 2020, 10:16 PM · segv, gpgme, Bug Report
nmset added a comment to T5151: GPGME++ : bad passphrase problems.

relatively new feature

Yes. In the mean time, I'm using a cheap workaround : validate the input passphrase by signing a dummy text before exporting. Not that ugly and can stay for long.

Nov 25 2020, 8:33 AM · segv, gpgme, Bug Report
gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

More specifically, in the situation of multiple calls, ->getPassphrase is called multiple times, and it should return newly allocated "char *" object each time, because it is released each time (in lower layer).

Nov 25 2020, 1:22 AM · segv, gpgme, Bug Report
gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

My excuse: Please note that the support of exporting secret keys by GPGME are relatively new feature (see {T5046) and the fix rM3382ecb17eb5: core: Support exporting secret keys.). The fix of rM53ac732bae46: core: Call _gpgme_passphrase_status_handler when exporting keys. is a part of the support.
I think that we need more fixes for gpg/gpgme to be fully working well.

Nov 25 2020, 12:51 AM · segv, gpgme, Bug Report

Nov 24 2020

nmset added a comment to T5151: GPGME++ : bad passphrase problems.

when passphrase is wrong, the passphrase callback is called more than one time (one for primary key, and another for a subkey, more if there are more subkeys).

Nov 24 2020, 9:30 AM · segv, gpgme, Bug Report
gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

Currently, gpg doesn't report any errors to status line for exporting secret keys. If needed, a patch like this is needed:

Nov 24 2020, 8:12 AM · segv, gpgme, Bug Report
gniibe added a comment to T5151: GPGME++ : bad passphrase problems.

Chasing this bug, I pushed a change: rM53ac732bae46: core: Call _gpgme_passphrase_status_handler when exporting keys.

Nov 24 2020, 7:08 AM · segv, gpgme, Bug Report

Nov 23 2020

ikloecker added a comment to T5151: GPGME++ : bad passphrase problems.
In T5151#139353, @nmset wrote:

Using Context::setExpire(), expiry time of keys and subkeys can be changed in a predictable way, with good and bad passphrase (fails with error of course).

Nov 23 2020, 12:30 PM · segv, gpgme, Bug Report
nmset added a comment to T5151: GPGME++ : bad passphrase problems.

I highly recommend to use the new ChangeExpiryJob instead of the fragile (and apparently buggy) edit interactor.

Nov 23 2020, 11:56 AM · segv, gpgme, Bug Report
nmset added a comment to T5151: GPGME++ : bad passphrase problems.

Can you try if using the overload

Nov 23 2020, 11:06 AM · segv, gpgme, Bug Report
ikloecker added a comment to T5151: GPGME++ : bad passphrase problems.

Can you try if using the overload

Error Context::exportPublicKeys(const char *patterns[], Data &keyData, unsigned int flags)

which takes an array of patterns instead of a single pattern also crashes?

Nov 23 2020, 10:15 AM · segv, gpgme, Bug Report
ikloecker added a comment to T5151: GPGME++ : bad passphrase problems.

Unless you need some special features of GpgSetExpiryTimeEditInteractor or you have to support gpgme <1.15, I highly recommend to use the new ChangeExpiryJob instead of the fragile (and apparently buggy) edit interactor.

Nov 23 2020, 10:06 AM · segv, gpgme, Bug Report

Nov 22 2020

werner triaged T5151: GPGME++ : bad passphrase problems as High priority.
Nov 22 2020, 10:22 AM · segv, gpgme, Bug Report

Nov 20 2020

lovetox updated the task description for T5149: Incorrect error handling in export_key_minimal().
Nov 20 2020, 9:29 PM · Python, gpgme, Bug Report
werner triaged T5149: Incorrect error handling in export_key_minimal() as Normal priority.
Nov 20 2020, 9:19 AM · Python, gpgme, Bug Report

Nov 19 2020

lovetox updated the task description for T5149: Incorrect error handling in export_key_minimal().
Nov 19 2020, 11:17 PM · Python, gpgme, Bug Report
lovetox created T5149: Incorrect error handling in export_key_minimal().
Nov 19 2020, 11:16 PM · Python, gpgme, Bug Report

Nov 18 2020

ikloecker closed T5142: Qt gpgme's sign_key function should not set a remark with an empty string as Resolved.

Fixed. Workaround for gpgme 1.15 (and earlier) implemented in Kleopatra: Do not call setRemark() with an empty QString.

Nov 18 2020, 1:55 PM · gpgme, qt, Bug Report
ikloecker added a comment to T5142: Qt gpgme's sign_key function should not set a remark with an empty string.

I think Kleopatra is affected. It calls setRemark() on the job unconditionally with the text from the widget, and I'm pretty sure that this text is empty but not a null QString, if the user doesn't enter a remark.

Nov 18 2020, 12:24 PM · gpgme, qt, Bug Report
werner assigned T5142: Qt gpgme's sign_key function should not set a remark with an empty string to ikloecker.

Ingo, can you please check? I guess we are not affected because Kleo already checks for an empty string. But dkg's suggestion sounds good to me.

Nov 18 2020, 10:34 AM · gpgme, qt, Bug Report
dkg created T5142: Qt gpgme's sign_key function should not set a remark with an empty string.
Nov 18 2020, 9:38 AM · gpgme, qt, Bug Report

Nov 13 2020

gniibe closed T5074: Leaking fd as Resolved.
Nov 13 2020, 7:17 AM · Testing, gpgme, Bug Report
gniibe closed T4688: `make distcheck` fails trying to make `rst/gpgme-python-howto.rst` as Resolved.
Nov 13 2020, 7:17 AM · Testing, gpgme, Bug Report

Nov 12 2020

gniibe added a comment to T4800: python-gpgme signature revokation assertion error: `gpg->cmd.code' failed.

Thanks for your report, but your excerpt is irrelevant.

Nov 12 2020, 9:11 AM · gpgme, Bug Report
gniibe closed T5046: Exporting secret keys via gpgme as Resolved.

Push the change.

Nov 12 2020, 5:15 AM · gpgme, Bug Report
gniibe claimed T5046: Exporting secret keys via gpgme.

Thank you.

Nov 12 2020, 5:10 AM · gpgme, Bug Report

Nov 11 2020

werner created T5131: Release GPGME 1.15.0.
Nov 11 2020, 5:08 PM · gpgme, Release Info

Oct 28 2020

gniibe closed T5075: [python-gpgme] Traceback when running with python -OO as Resolved.

Pushed the change.

Oct 28 2020, 12:51 AM · gpgme, Python, Bug Report
gniibe claimed T5075: [python-gpgme] Traceback when running with python -OO.
Oct 28 2020, 12:30 AM · gpgme, Python, Bug Report

Oct 27 2020

gniibe added a comment to T5075: [python-gpgme] Traceback when running with python -OO.

IIUC, fix can be like this:

diff --git a/lang/python/src/core.py b/lang/python/src/core.py
index 996c3b0f..646bbc60 100644
--- a/lang/python/src/core.py
+++ b/lang/python/src/core.py
@@ -147,7 +147,12 @@ class GpgmeWrapper(object):
                     gpgme.gpg_raise_callback_exception(slf)
                 return result
Oct 27 2020, 8:31 AM · gpgme, Python, Bug Report

Oct 3 2020

werner closed T5088: gpgme-1-13-1 test failure and errors and build errors as Resolved.
Oct 3 2020, 7:55 PM · gpgme, toolchain, Bug Report

Oct 1 2020

gniibe changed the status of T5074: Leaking fd from Open to Testing.
Oct 1 2020, 4:21 AM · Testing, gpgme, Bug Report
gniibe claimed T5074: Leaking fd.

Good catch. Thank you.

Oct 1 2020, 4:18 AM · Testing, gpgme, Bug Report
gniibe accepted D508: Close unused fd.
Oct 1 2020, 4:18 AM · gpgme

Sep 26 2020

despair created D508: Close unused fd.
Sep 26 2020, 9:23 AM · gpgme

Sep 18 2020

mathieui created T5075: [python-gpgme] Traceback when running with python -OO.
Sep 18 2020, 5:11 PM · gpgme, Python, Bug Report
despair created T5074: Leaking fd.
Sep 18 2020, 8:29 AM · Testing, gpgme, Bug Report

Sep 7 2020

bernhard renamed T5046: Exporting secret keys via gpgme from Exporting secret keys to Exporting secret keys via gpgme.
Sep 7 2020, 10:17 AM · gpgme, Bug Report

Sep 5 2020

dblouis added a comment to T5046: Exporting secret keys via gpgme.

The following patch make it work:

Sep 5 2020, 7:35 PM · gpgme, Bug Report
dblouis updated the task description for T5046: Exporting secret keys via gpgme.
Sep 5 2020, 7:03 PM · gpgme, Bug Report

Sep 2 2020

dblouis updated the task description for T5046: Exporting secret keys via gpgme.
Sep 2 2020, 5:41 PM · gpgme, Bug Report
dblouis created T5046: Exporting secret keys via gpgme.
Sep 2 2020, 5:30 PM · gpgme, Bug Report

Aug 29 2020

werner added a comment to T5037: dn.cpp:181: suspicious loop.

FWIW, here an example of warnings we use. Yes it starts with -Wall but there are a couple of more specific warnings and at a few places we even use pragmas to disable warnings. And it depends on the compiler version used.

Aug 29 2020, 5:16 PM · gnupg, gpgme, Bug Report

Aug 28 2020

dcb added a comment to T5037: dn.cpp:181: suspicious loop.

-Wall is not a good idea in general because it is too unspecific. This is why we have a list of useful warning and >warnings we ignore with gcc.

Aug 28 2020, 7:53 PM · gnupg, gpgme, Bug Report
werner added a comment to T5037: dn.cpp:181: suspicious loop.

-Wall is not a good idea in general because it is too unspecific. This is why we have a list of useful warning and warnings we ignore with gcc.

Aug 28 2020, 12:43 PM · gnupg, gpgme, Bug Report
dcb added a comment to T5037: dn.cpp:181: suspicious loop.

I found the bug by compiling the package with C/C++ compiler clang and flag -Wall.

Aug 28 2020, 9:32 AM · gnupg, gpgme, Bug Report
werner closed T5037: dn.cpp:181: suspicious loop as Resolved.

Fixed in gnupg and gpgme. it is not serious because that is just a failsafe check; libksba creates these strings and it does it correctly.

Aug 28 2020, 9:15 AM · gnupg, gpgme, Bug Report
werner added a project to T5037: dn.cpp:181: suspicious loop: gnupg.

We have the same flaw in gnupg.

Aug 28 2020, 9:00 AM · gnupg, gpgme, Bug Report
werner claimed T5037: dn.cpp:181: suspicious loop.
Aug 28 2020, 8:54 AM · gnupg, gpgme, Bug Report
gniibe added a project to T5037: dn.cpp:181: suspicious loop: gpgme.
Aug 28 2020, 3:06 AM · gnupg, gpgme, Bug Report

Aug 14 2020

ikloecker changed the status of T4395: Kleopatra: Missing error handling when changing expiry from Open to Testing.

Fixed.

Aug 14 2020, 12:01 PM · gpa, gnupg, gpgme, gpg4win, kleopatra

Aug 13 2020

ikloecker claimed T4395: Kleopatra: Missing error handling when changing expiry.

Taking: Still does not work although now --quick-set-expire is used by gpgme.

Aug 13 2020, 4:47 PM · gpa, gnupg, gpgme, gpg4win, kleopatra
werner closed T4793: New GPGME API to support card personalization as Wontfix.

We won't do such a interface now.

Aug 13 2020, 3:22 PM · scd, gpgme

Aug 12 2020

ikloecker changed the status of T5003: GpgME++: Add support for gpgme_set_expire, a subtask of T4999: GPGME: Add interface for quick-set-expire, from Open to Testing.
Aug 12 2020, 12:28 PM · gpgme, kleopatra, gpg4win

Aug 6 2020

aheinecke closed T4999: GPGME: Add interface for quick-set-expire as Resolved.

Thanks. rMdb82e99 resolved this.

Aug 6 2020, 10:18 AM · gpgme, kleopatra, gpg4win
aheinecke lowered the priority of T4854: gpgme 1.13.1: test suite is failing from Normal to Low.

I just ran the test suite ~10 Times with -j48 on a 12 core machine and cannot reproduce this at all with GnuPG-2.2.21 and gpgme-1.14.0 so I tend to put this on resolved, otherwise this is a candidate for an issue that will be indefinetly in the tracker which we cannot reproduce or analyze further.

Aug 6 2020, 10:12 AM · gpgme, Bug Report
aheinecke triaged T4854: gpgme 1.13.1: test suite is failing as Normal priority.

The t-json failure is: T4820

Aug 6 2020, 10:02 AM · gpgme, Bug Report
aheinecke closed T5013: OS X 10.11 and error: use of undeclared identifier 'getenv' as Resolved.
Aug 6 2020, 9:59 AM · gpgme, Bug Report
aheinecke added a comment to T5013: OS X 10.11 and error: use of undeclared identifier 'getenv'.

Thanks, I've applied this with an explicit include to <cstdlib> it was not required on Linux and Windows but I think it's better not to rely on internal libc++ include chains.

Aug 6 2020, 9:54 AM · gpgme, Bug Report
gniibe added a comment to T5013: OS X 10.11 and error: use of undeclared identifier 'getenv'.

Thanks for your report.

Aug 6 2020, 5:59 AM · gpgme, Bug Report

Aug 5 2020

JW added a comment to T5013: OS X 10.11 and error: use of undeclared identifier 'getenv'.

According to OS X 10.9 man pages for getenv(3) (10.9 is what I have available), the source file editinteractor.cpp should include <stdlib.h>. Since its a c++ source file, I believe the include of interest is <cstdlib>. The man page also says the link library is -lc.

Aug 5 2020, 7:57 PM · gpgme, Bug Report
JW updated the task description for T5013: OS X 10.11 and error: use of undeclared identifier 'getenv'.
Aug 5 2020, 7:55 PM · gpgme, Bug Report
JW created T5013: OS X 10.11 and error: use of undeclared identifier 'getenv'.
Aug 5 2020, 7:53 PM · gpgme, Bug Report

Jul 27 2020

aheinecke added a comment to T4999: GPGME: Add interface for quick-set-expire.

Phabricator allows it again to upload patches. It's D507

Jul 27 2020, 3:46 PM · gpgme, kleopatra, gpg4win
aheinecke created D507: core: Add gpgme_op_set_expire.
Jul 27 2020, 3:45 PM · gpgme
aheinecke added a revision to T4999: GPGME: Add interface for quick-set-expire: D507: core: Add gpgme_op_set_expire.
Jul 27 2020, 3:45 PM · gpgme, kleopatra, gpg4win
aheinecke added a subtask for T4999: GPGME: Add interface for quick-set-expire: T5003: GpgME++: Add support for gpgme_set_expire.
Jul 27 2020, 2:52 PM · gpgme, kleopatra, gpg4win

Jul 17 2020

werner closed T4310: GPGME: Add ssh export mode as Resolved.

C++ interface is also availabale in 1.14.0 (see rM690d967196d9).

Jul 17 2020, 12:06 PM · Feature Request, gpgme
werner closed T4820: gpgme's json test fails with gpg 2.2.19 as Resolved.
Jul 17 2020, 11:41 AM · gpgme, Bug Report
werner closed T4996: Release GPGME 1.14.0 as Resolved.
Jul 17 2020, 11:25 AM · gpgme, Release Info
werner updated the task description for T4996: Release GPGME 1.14.0.
Jul 17 2020, 11:01 AM · gpgme, Release Info
aheinecke created T4999: GPGME: Add interface for quick-set-expire.
Jul 17 2020, 9:53 AM · gpgme, kleopatra, gpg4win

Jul 16 2020

werner created T4996: Release GPGME 1.14.0.
Jul 16 2020, 5:13 PM · gpgme, Release Info
werner added a project to T3957: GPGME: mkdefsinc segfaults on windows: unreproducible.
Jul 16 2020, 3:29 PM · unreproducible, toolchain, Documentation, Windows, gpgme
werner closed T3957: GPGME: mkdefsinc segfaults on windows as Invalid.

No info received

Jul 16 2020, 3:27 PM · unreproducible, toolchain, Documentation, Windows, gpgme
werner added a project to T3794: GPGME: Make it possible to switch trust model per context: Feature Request.
Jul 16 2020, 3:21 PM · Feature Request, gpgol, gpgme
werner closed T3515: Gpg4win: Gpgconf used to open "windows" and slows down kleo startup as Resolved.

I am not any longer interested to see the real cause; eventually we will replace it anyway with a modern CreateProcess.

Jul 16 2020, 3:19 PM · Windows, gpgme
werner closed T3512: gpgme test failure when run with gpg version 1 as Invalid.

Reconsidering this: Running the test suite with gpg1 is not a proper use case. gpg1 may be installed in addition to gpg but it should never be used on a build machine solely.

Jul 16 2020, 3:09 PM · gnupg (gpg14), gpgme, Bug Report
werner lowered the priority of T3512: gpgme test failure when run with gpg version 1 from Normal to Low.
Jul 16 2020, 3:07 PM · gnupg (gpg14), gpgme, Bug Report
werner closed T3413: gpgme_op_delete doesn't return failure when loopback mode is enabled as Wontfix.
Jul 16 2020, 2:53 PM · gpgme, Bug Report
werner closed T3396: use swig to generate Ruby bindings for gpgme as Wontfix.

As of today we don't want to maintain another binding; see T3395

Jul 16 2020, 2:52 PM · Feature Request, gpgme
werner closed T3395: use swig to generate Perl bindings for gpgme as Wontfix.

The Python bindings are troublesome enough; as of today we don't want to maintain a Perl module.

Jul 16 2020, 2:51 PM · Feature Request, gpgme
werner closed T3356: gpgme test suite failure in lang/qt/tests/t-config.cpp on mipsel as Invalid.

No info received in3 years.

Jul 16 2020, 2:49 PM · Too Old, gpgme, Bug Report
werner closed T3348: gpgsm: should default to --disable-crl-checks as Wontfix.
Jul 16 2020, 2:45 PM · gpgme, gnupg, S/MIME