Page MenuHome GnuPG
Feed Advanced Search

Wed, Oct 20

ikloecker added a comment to T5668: gpgme: gpgme_op_query_swdb() does not report error from gpgconf.

The below change makes the function report a general error if gpgconf didn't write any output on stdout:

diff --git a/src/engine-gpgconf.c b/src/engine-gpgconf.c
index 28f91158..21211366 100644
--- a/src/engine-gpgconf.c
+++ b/src/engine-gpgconf.c
@@ -1245,6 +1245,13 @@ gpgconf_query_swdb (void *engine,
         }
     }
Wed, Oct 20, 3:45 PM · Restricted Project, gpgme, Bug Report
ikloecker created T5668: gpgme: gpgme_op_query_swdb() does not report error from gpgconf.
Wed, Oct 20, 3:42 PM · Restricted Project, gpgme, Bug Report

Tue, Oct 5

gniibe set External Link to https://src.fedoraproject.org/rpms/libgcrypt/blob/rawhide/f/libgcrypt-1.8.4-use-poll.patch on T5637: Use poll for libgcrypt (support more than 1024 fds).
Tue, Oct 5, 6:32 AM · gpgrt, Feature Request, gpgme
gniibe triaged T5637: Use poll for libgcrypt (support more than 1024 fds) as High priority.
Tue, Oct 5, 6:31 AM · gpgrt, Feature Request, gpgme

Mon, Oct 4

werner raised the priority of T2385: support more than 1024 fds. from Normal to High.
Mon, Oct 4, 11:08 AM · gpgrt, Feature Request, gpgme

Wed, Sep 29

Jakuje added a comment to T2385: support more than 1024 fds..

Hi, was there any update on this? I found the following bug [0] in libgcrypt, which we solved [1] with using poll ages ago.

Wed, Sep 29, 6:13 PM · gpgrt, Feature Request, gpgme

Sep 21 2021

werner closed T5615: pgpme fails compiling: void value not ignored as Resolved.

Please see T5587

Sep 21 2021, 8:44 PM · gpgme, Duplicate, Bug Report

Sep 8 2021

ikloecker closed T5591: How to build Gpgmepp in Windows 10 as Invalid.

Please talk to the KDE folks who develop Craft. We do not support building anything with Craft. Check out gpg4win (https://dev.gnupg.org/source/gpg4win/) to see how we build our products on Windows.

Sep 8 2021, 10:39 AM · Cross-Compiler, gpgme
kashif created T5591: How to build Gpgmepp in Windows 10.
Sep 8 2021, 10:19 AM · Cross-Compiler, gpgme

Sep 5 2021

ffontaine added a comment to T5587: src/posix-io.c: fix build with glibc >= 2.34.

Nevermind, I found the appropriate link above, thanks again.

Sep 5 2021, 7:05 PM · gpgme
ffontaine added a comment to T5587: src/posix-io.c: fix build with glibc >= 2.34.

Thanks for noticing me but I can't access your git repository at https://dev.gnupg.org/source/gnupg.git and the github mirror at https://github.com/gpg/gpgme is not up to date. Do you have an other mirror?

Sep 5 2021, 7:03 PM · gpgme
werner closed T5587: src/posix-io.c: fix build with glibc >= 2.34 as Resolved.

Thanks. This has already been fixed in July with rM4b64774b6d13ffa4f59dddf947a97d61bcfa2f2e

Sep 5 2021, 11:47 AM · gpgme
ffontaine updated the task description for T5587: src/posix-io.c: fix build with glibc >= 2.34.
Sep 5 2021, 12:14 AM · gpgme
ffontaine created T5587: src/posix-io.c: fix build with glibc >= 2.34.
Sep 5 2021, 12:13 AM · gpgme

Sep 1 2021

gniibe set External Link to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102151 on T5556: Use of offsetof is better for allocation of flexible array.
Sep 1 2021, 3:44 AM · gnupg (gpg23), gpgme, libgcrypt
gniibe added a comment to T5556: Use of offsetof is better for allocation of flexible array.

I filed a bug report to GCC, with modified test case.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102151

Sep 1 2021, 3:43 AM · gnupg (gpg23), gpgme, libgcrypt
gniibe claimed T5556: Use of offsetof is better for allocation of flexible array.
Sep 1 2021, 2:54 AM · gnupg (gpg23), gpgme, libgcrypt

Aug 25 2021

werner triaged T5556: Use of offsetof is better for allocation of flexible array as Normal priority.
Aug 25 2021, 4:27 PM · gnupg (gpg23), gpgme, libgcrypt

Aug 24 2021

gniibe added a comment to T5556: Use of offsetof is better for allocation of flexible array.
t-fam.c: In function 'main':
t-fam.c:34:14: warning: array subscript 'struct arg_and_data_s[0]' is partly outside array bounds of 'unsigned char[22]' [-Warray-bounds]
   34 |   aad0->next = NULL;
      |              ^
t-fam.c:30:10: note: referencing an object of size 22 allocated by 'malloc'
   30 |   aad0 = malloc (offsetof (struct arg_and_data_s, arg) + 2);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t-fam.c:35:13: warning: array subscript 'struct arg_and_data_s[0]' is partly outside array bounds of 'unsigned char[22]' [-Warray-bounds]
   35 |   aad0->len = 2;
      |   ~~~~~~~~~~^~~
t-fam.c:30:10: note: referencing an object of size 22 allocated by 'malloc'
   30 |   aad0 = malloc (offsetof (struct arg_and_data_s, arg) + 2);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t-fam.c:36:15: warning: array subscript 'struct arg_and_data_s[0]' is partly outside array bounds of 'unsigned char[22]' [-Warray-bounds]
   36 |   aad0->flags = 0;
      |   ~~~~~~~~~~~~^~~
t-fam.c:30:10: note: referencing an object of size 22 allocated by 'malloc'
   30 |   aad0 = malloc (offsetof (struct arg_and_data_s, arg) + 2);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
t-fam.c:37:18: warning: array subscript 'struct arg_and_data_s[0]' is partly outside array bounds of 'unsigned char[22]' [-Warray-bounds]
   37 |   aad0->print_fd = fd;
      |   ~~~~~~~~~~~~~~~^~~~
t-fam.c:30:10: note: referencing an object of size 22 allocated by 'malloc'
   30 |   aad0 = malloc (offsetof (struct arg_and_data_s, arg) + 2);
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Aug 24 2021, 7:29 AM · gnupg (gpg23), gpgme, libgcrypt
gniibe added a comment to T5556: Use of offsetof is better for allocation of flexible array.

For GCC 11, modified version of struct arg_and_data_s has an issue for x86_64.

Aug 24 2021, 4:53 AM · gnupg (gpg23), gpgme, libgcrypt

Aug 23 2021

gniibe added a comment to T5556: Use of offsetof is better for allocation of flexible array.

For the use case of struct arg_and_data_s in gpgme, which may allocate zero-sized ARG[], it seems that GCC 11 interprets it as an invalid use.

Aug 23 2021, 6:25 AM · gnupg (gpg23), gpgme, libgcrypt
gniibe added projects to T5556: Use of offsetof is better for allocation of flexible array: libgcrypt, gpgme, gnupg (gpg23).
Aug 23 2021, 4:47 AM · gnupg (gpg23), gpgme, libgcrypt

Aug 17 2021

aheinecke triaged T5558: GPGME: No error handling for symmetric encryption as Normal priority.
Aug 17 2021, 11:45 AM · gpgme

Aug 13 2021

werner changed the edit policy for gpgme.
Aug 13 2021, 11:03 PM

Jul 28 2021

bernhard added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

dlopen'ing of gpgme is NOT SUPPORTED. It is in general not a good idea to do this on standard Unix systems.

Jul 28 2021, 11:08 AM · gpgme, MacOS, Bug Report
werner added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

To extend on this: dlopen'ing of gpgme is NOT SUPPORTED. It is in general not a good idea to do this on standard Unix systems. On Windows we could make it work because DLLs on that platform are well designed and not a hack like the Unix shared objects.

Jul 28 2021, 9:49 AM · gpgme, MacOS, Bug Report

Jul 27 2021

aheinecke claimed T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

We really want thunderbird users that interact with GPGME to have a great and stable user experience, but the problem with dynamic loading and self compiled versions is that we cannot really know the build settings and enviornment and it is very time consuming to reproduce that. GPGME does some very low level things for optimized IPC that can depend on build options etc. This is why I am mostly in favor that thunderbird ships a defined version that we can debug and see the settings.

Jul 27 2021, 4:47 PM · gpgme, MacOS, Bug Report
bernhard added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

Reading the mozilla entry more carefully, there still seems to be an issue.

Jul 27 2021, 10:58 AM · gpgme, MacOS, Bug Report
bernhard added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

https://blog.gerv.net/2012/01/mozilla-projects-and-gpled-code/

@kaie, thanks for the pointer!

Jul 27 2021, 10:27 AM · gpgme, MacOS, Bug Report

Jul 26 2021

kaie added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

BTW @kaie

Thunderbird cannot use anything requiring GPL in its default configuration, because Thunderbird wants to distribute a single MPL licensed package that includes all components that are required for OpenPGP.

Any pointer why, they have made that choice, though? A bundle of MPL and GNU GPL components is fully allowed by the licenses as far as I know.

Jul 26 2021, 11:59 PM · gpgme, MacOS, Bug Report

Jul 24 2021

bernhard added a comment to T5250: macOS: gpgconf SIGSEGV when run via gpgme from the GUI application.

Using GPGME is probably the best way, even if gpgme-json might also work for some operations.

Jul 24 2021, 4:52 PM · gpgme, MacOS, Bug Report

Jul 19 2021

ikloecker merged T5526: GPGME: Qt test t-various fails on i386 into T5522: gpgme: qt: t-various.cpp TestVarious::testSignKeyWithExpiration fails on 32 bit.
Jul 19 2021, 10:25 AM · gpgme, Bug Report
ikloecker merged task T5526: GPGME: Qt test t-various fails on i386 into T5522: gpgme: qt: t-various.cpp TestVarious::testSignKeyWithExpiration fails on 32 bit.
Jul 19 2021, 10:25 AM · gpgme, Bug Report
ikloecker closed T5526: GPGME: Qt test t-various fails on i386 as Resolved.

This is a duplicate of T5522: gpgme: qt: t-various.cpp TestVarious::testSignKeyWithExpiration fails on 32 bit.

Jul 19 2021, 10:22 AM · gpgme, Bug Report

Jul 8 2021

ikloecker closed T5522: gpgme: qt: t-various.cpp TestVarious::testSignKeyWithExpiration fails on 32 bit as Resolved.
Jul 8 2021, 2:21 PM · gpgme, Bug Report
andreasstieger added a comment to T5522: gpgme: qt: t-various.cpp TestVarious::testSignKeyWithExpiration fails on 32 bit.

rM6a79e90dedc19877ae1c520fed875b57089a5425 looks good

Jul 8 2021, 1:44 PM · gpgme, Bug Report
ikloecker claimed T5522: gpgme: qt: t-various.cpp TestVarious::testSignKeyWithExpiration fails on 32 bit.
Jul 8 2021, 11:42 AM · gpgme, Bug Report

Jul 7 2021

andreasstieger created T5522: gpgme: qt: t-various.cpp TestVarious::testSignKeyWithExpiration fails on 32 bit.
Jul 7 2021, 8:56 PM · gpgme, Bug Report
Saturneric added a comment to T5468: About the API of GpgME to revoke key pairs and subkeys..

Thanks for the reply, this source code file and suggestions are very useful. Let gpg execute commands is a solution, but it is not optimal compared to providing a functional interface.
In addition, it is reversible to revoke the subkey by expiring it. But I will use the solutions you provide at this stage, knowing that you have time to provide better solutions. thank you!

Jul 7 2021, 6:26 PM · gpgme, Feature Request
ikloecker added a comment to T5468: About the API of GpgME to revoke key pairs and subkeys..

What do you mean by "exporting revocation certificates"? Once such a certificate is imported you simply export the public key including the revocation signature. Otherwise, simply takes the revocation certificates from ${GNUPGHOME}/openpgp-revocs.d where they are written to, if you generate a key. Kleopatra uses gpg directly to generate a revocation certificate mimicking what gpgme would do: See https://dev.gnupg.org/source/kleo/browse/master/src/commands/genrevokecommand.cpp.

Jul 7 2021, 10:24 AM · gpgme, Feature Request

Jul 6 2021

werner triaged T5468: About the API of GpgME to revoke key pairs and subkeys. as Normal priority.
Jul 6 2021, 6:10 PM · gpgme, Feature Request

Jun 29 2021

ikloecker closed T5515: qgpgme: Allow retrieving the default value of a config entry as Resolved.
Jun 29 2021, 12:31 PM · gpgme, Restricted Project, kleopatra
ikloecker moved T5515: qgpgme: Allow retrieving the default value of a config entry from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Jun 29 2021, 12:31 PM · gpgme, Restricted Project, kleopatra
ikloecker moved T5515: qgpgme: Allow retrieving the default value of a config entry from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Jun 29 2021, 11:56 AM · gpgme, Restricted Project, kleopatra
ikloecker triaged T5515: qgpgme: Allow retrieving the default value of a config entry as Normal priority.
Jun 29 2021, 11:56 AM · gpgme, Restricted Project, kleopatra

Jun 26 2021

ikloecker closed T5509: Use-after-free in t-edit-sign test as Resolved.

Thanks for the report. Fixed.

Jun 26 2021, 6:07 PM · gpgme, Bug Report

Jun 25 2021

werner assigned T5509: Use-after-free in t-edit-sign test to ikloecker.

Thanks for the report.

Jun 25 2021, 5:49 PM · gpgme, Bug Report
atsampson created T5509: Use-after-free in t-edit-sign test.
Jun 25 2021, 5:07 PM · gpgme, Bug Report
werner added a project to T5500: gpgme: Test t-idiomatic.py fails with Python 3.8: Python.
Jun 25 2021, 9:16 AM · Python, gpgme, Bug Report
werner triaged T5500: gpgme: Test t-idiomatic.py fails with Python 3.8 as Normal priority.

We need to see how to best fix this regression test for all Python versions.

Jun 25 2021, 9:16 AM · Python, gpgme, Bug Report

Jun 24 2021

werner updated the task description for T5499: Release GPGME 1.16.0.
Jun 24 2021, 7:48 PM · Release Info, gpgme
werner closed T5292: regression: no longer possible to get signatures from decrypt from unknown keys as Resolved.
Jun 24 2021, 7:43 PM · patch, Python, gpgme, Bug Report
werner closed T5499: Release GPGME 1.16.0 as Resolved.
Jun 24 2021, 7:40 PM · Release Info, gpgme
werner lowered the priority of T3958: GPGME: Qt Bindings and MacOS from Normal to Low.
Jun 24 2021, 6:31 PM · MacOS, qt, gpgme
werner moved T4276: Context.decrypt() throws an error if *any* signature is bad from Backlog to Python on the gpgme board.
Jun 24 2021, 6:30 PM · gpgme, Python, Bug Report
werner renamed T5284: Allow gpgme to export w/o attributes from gpgme uses incorrect flags for minimal, no uid export of public keys to Allow gpgme to export w/o attributes.
Jun 24 2021, 6:24 PM · Feature Request, gpgme
werner moved T5353: gpgme: Implement keylist_data for gpgsm from Backlog to For a future release on the gpgme board.
Jun 24 2021, 6:21 PM · gnupg (gpg23), gpgme, Feature Request
werner moved T5438: gpgme_op_keylist_from_data_start ignores GPGME_KEYLIST_MODE_SIGS from Backlog to For a future release on the gpgme board.
Jun 24 2021, 6:21 PM · OpenPGP, Bug Report, gpgme
werner moved T5500: gpgme: Test t-idiomatic.py fails with Python 3.8 from Backlog to Python on the gpgme board.
Jun 24 2021, 6:00 PM · Python, gpgme, Bug Report
werner closed T4939: GPGME: Add KEYLIST_MODE_WITH_KEYGRIP as Resolved.

Was released with 1.14.0 see T4996

Jun 24 2021, 5:56 PM · gpgme

Jun 23 2021

ikloecker closed T5505: gpgme: Allow specifying an expiration date for key signatures (gpgme_op_interact) as Resolved.
Jun 23 2021, 4:58 PM · gpgme, kleopatra, Restricted Project
ikloecker moved T5505: gpgme: Allow specifying an expiration date for key signatures (gpgme_op_interact) from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Jun 23 2021, 4:57 PM · gpgme, kleopatra, Restricted Project

Jun 22 2021

ikloecker moved T5505: gpgme: Allow specifying an expiration date for key signatures (gpgme_op_interact) from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Jun 22 2021, 4:39 PM · gpgme, kleopatra, Restricted Project
ikloecker triaged T5505: gpgme: Allow specifying an expiration date for key signatures (gpgme_op_interact) as Wishlist priority.
Jun 22 2021, 4:31 PM · gpgme, kleopatra, Restricted Project

Jun 21 2021

werner triaged T5503: Add APIs to sign (and encrypt?) with a specific subkey as Normal priority.
Jun 21 2021, 5:16 PM · gpgme, Feature Request
ikloecker created T5500: gpgme: Test t-idiomatic.py fails with Python 3.8.
Jun 21 2021, 10:54 AM · Python, gpgme, Bug Report
werner updated the task description for T5225: Release GPGME 1.15.1.
Jun 21 2021, 10:29 AM · Release Info, gpgme
werner triaged T5499: Release GPGME 1.16.0 as Normal priority.
Jun 21 2021, 10:28 AM · Release Info, gpgme

Jun 19 2021

Saturneric closed T5489: GpgME Built by mingw64 didn’t seem to correctly recognize the configuration information provided by gpgconf as Resolved.
Jun 19 2021, 2:49 PM · gpgme, Bug Report
Saturneric added a comment to T5489: GpgME Built by mingw64 didn’t seem to correctly recognize the configuration information provided by gpgconf .

The problem has been solved by me, but this and the problem are still very strange.

Jun 19 2021, 2:48 PM · gpgme, Bug Report

Jun 17 2021

werner added a comment to T5489: GpgME Built by mingw64 didn’t seem to correctly recognize the configuration information provided by gpgconf .

Please try the distributed binary version of gpgme from GnuPG or Gpg4win (which is usually a snapshot). As you might now, we don't support building on Windows - it may or may not work, we have no idea and don't suggest that.

Jun 17 2021, 11:42 AM · gpgme, Bug Report

Jun 16 2021

Saturneric added a comment to T5489: GpgME Built by mingw64 didn’t seem to correctly recognize the configuration information provided by gpgconf .

Let me explain this problem more clearly. GPGME did not correctly receive and parse the output from gpgconf. Looking at the log file, EOF was generated when 4096 bits were read. So in engine info, although the path is correct, the identification of the version number is 1.0.0, and there is only gpgconf in the protocol, but there are no protocols such as gpg, assume, etc., which just means that gpgme does not correctly identify the output of gpgconf in this environment Information to find other protocols.
At the same time, I verified whether the output in gpgconf and the path of the related configuration are correct (whether there is a corresponding tool under the path), these are all right, which is very strange.

Jun 16 2021, 6:44 PM · gpgme, Bug Report
Saturneric added a comment to T5489: GpgME Built by mingw64 didn’t seem to correctly recognize the configuration information provided by gpgconf .

This is the log file output after the GPGME DEBUG environment variable is set.

Jun 16 2021, 5:35 PM · gpgme, Bug Report
werner added a project to T5489: GpgME Built by mingw64 didn’t seem to correctly recognize the configuration information provided by gpgconf : gpgme.

You should run your test program with GPGME_DEBUG set. This gives some insight. The code you posted is too sparse to actually see what you are doing or want to do or what is the bug. Maybe it is better to ask the gnupg-devel ML?

Jun 16 2021, 5:32 PM · gpgme, Bug Report

Jun 10 2021

aheinecke added a project to T5478: Kleopatra: Performance problems decrypting and encrypting large Archives: Restricted Project.
Jun 10 2021, 3:49 PM · Restricted Project, gpgme, kleopatra
aheinecke triaged T5478: Kleopatra: Performance problems decrypting and encrypting large Archives as High priority.
Jun 10 2021, 1:11 PM · Restricted Project, gpgme, kleopatra

Jun 3 2021

werner merged T5470: T5454 Continue Gpgme still shows secret flag even when the secret key content is missing into T5454: Failed to sign with subkey with a signature function using gpgme_op_keysign.
Jun 3 2021, 9:23 PM · FAQ, Support, gpgme
Saturneric closed T5454: Failed to sign with subkey with a signature function using gpgme_op_keysign as Resolved.
Jun 3 2021, 3:12 PM · FAQ, Support, gpgme

May 31 2021

werner added a comment to T5454: Failed to sign with subkey with a signature function using gpgme_op_keysign.

Take care: It is not clear whether you may use a [C} subkey for certification. GnuPG currently accepts this but the RFC can also be read as primary keys needs to to do the certification.

May 31 2021, 2:54 PM · FAQ, Support, gpgme
ikloecker added a comment to T5454: Failed to sign with subkey with a signature function using gpgme_op_keysign.

For signing (aka certifying) another key you need a (sub)key with the "certify" capability. Your signing subkey can only be used for signing data but not for certifying keys. This isn't specific to gpgme. See https://datatracker.ietf.org/doc/html/rfc4880#section-5.2.3.21.

May 31 2021, 9:44 AM · FAQ, Support, gpgme

May 28 2021

werner edited projects for T5454: Failed to sign with subkey with a signature function using gpgme_op_keysign, added: Support, FAQ; removed Bug Report.

Yes, you need the secret part of the primary key. gpgme has this info but it is easy to miss. Even our gpgme/tests/run-keylist.c debug tool did not show it directly. I modified it to make this more clear, see the latest gpgme commit. Here is an example for my key:

$ ./run-keylist --verbose --with-secret  63113AE866587D0A
keyid   : 63113AE866587D0A
caps    : esc
flags   : secret
upd     : 0 (0)
fpr    0: AEA84EDCF01AD86C4701C85C63113AE866587D0A
grip   0: CE5C1F1B8C96F1A078A2D1932EEE738A854ED976
curve  0: ed25519
caps   0: sc
flags  0:
fpr    1: E05BA20ED4F17768613B03C53CD7B3A055039224
grip   1: 7A1E3130C9CBDBF203A0AD8E186D9C511D5019FF
curve  1: cv25519
caps   1: e
flags  1: secret
fpr    2: 8777461F2A074EBC480D359419CC1C9E085B107A
grip   2: FF35C6E765F440145095750DC97D43D496C5ABEA
curve  2: ed25519
caps   2: s
flags  2: secret
May 28 2021, 7:32 PM · FAQ, Support, gpgme
werner added a project to T5454: Failed to sign with subkey with a signature function using gpgme_op_keysign: gpgme.
May 28 2021, 4:36 PM · FAQ, Support, gpgme

May 27 2021

werner triaged T5453: gpgme docs unclear about gpgme_user_id_t.email and gpgme_user_id_t.address as Wishlist priority.
May 27 2021, 7:53 AM · Documentation, gpgme, Bug Report
dkg created T5453: gpgme docs unclear about gpgme_user_id_t.email and gpgme_user_id_t.address.
May 27 2021, 4:17 AM · Documentation, gpgme, Bug Report

May 23 2021

werner closed T5448: GPG_ERR_EOF didn't return by gpgme_op_keylist_next after the last key in the list had already been returned as Resolved.
May 23 2021, 9:32 PM · Support, gpgme

May 17 2021

werner triaged T5438: gpgme_op_keylist_from_data_start ignores GPGME_KEYLIST_MODE_SIGS as High priority.

Due to tax issues, we can't accept a donation as return on service. However, we will fix bugs anyway if possible,

May 17 2021, 11:50 AM · OpenPGP, Bug Report, gpgme

May 16 2021

pert created T5438: gpgme_op_keylist_from_data_start ignores GPGME_KEYLIST_MODE_SIGS.
May 16 2021, 2:25 PM · OpenPGP, Bug Report, gpgme

May 7 2021

ikloecker closed T5422: gnupg 2.3.1 breaks gpgme_op_createkey() as Resolved.

You are welcome.

May 7 2021, 12:43 PM · gpgme, Bug Report
pnirschl added a comment to T5422: gnupg 2.3.1 breaks gpgme_op_createkey().

run-genkey is working fine in my test environment as well.

May 7 2021, 9:41 AM · gpgme, Bug Report

May 6 2021

ikloecker closed T5419: gpgme: Add support for trust signatures to key list result as Resolved.
May 6 2021, 3:15 PM · kleopatra, gpgme, Restricted Project
ikloecker moved T5419: gpgme: Add support for trust signatures to key list result from Restricted Project Column to Restricted Project Column on the Restricted Project board.
May 6 2021, 3:15 PM · kleopatra, gpgme, Restricted Project
ikloecker abandoned D530: gpgme: Add support for trust signatures to key list result.

This revision was committed with rM276187f6b62a: core: Extend gpgme_key_sig_t with trust signature members.

May 6 2021, 3:15 PM · gpgme
ikloecker set the repository for D530: gpgme: Add support for trust signatures to key list result to rM GPGME.
May 6 2021, 3:13 PM · gpgme
ikloecker moved T5419: gpgme: Add support for trust signatures to key list result from Restricted Project Column to Restricted Project Column on the Restricted Project board.
May 6 2021, 3:06 PM · kleopatra, gpgme, Restricted Project
werner added a comment to D530: gpgme: Add support for trust signatures to key list result.

This is better name. My point was that if we ever use that to create such a field the developer should not assume that arbitrary REs can be used here. We need to have some practical value here and I would prefer to see only the domain name. However, OpenPGP allows for arbitrary REs and thus we may see them here. This is problematic but we can't do much about it.

May 6 2021, 10:01 AM · gpgme
ikloecker added a comment to T5422: gnupg 2.3.1 breaks gpgme_op_createkey().

Well, all I can say is that
./run-genkey --loopback "elektra testkey (gen-gpg-testkey)"
creates a key without any problems and without asking for a passphrase. Even, if I add the GPGME_CREATE_NOEXPIRE flag to the call of gpgme_op_createkey. At least, from a terminal.

May 6 2021, 9:19 AM · gpgme, Bug Report

May 5 2021

pnirschl added a comment to T5422: gnupg 2.3.1 breaks gpgme_op_createkey().

Thank you for your response! I tried out all variants of gpgme_pinentry_mode_t and implemented a passphrase callback (using gpgme_set_passphrase_cb as suggested). It turns out that the callback is not invoked at all. However, if I switch back to gnupg 2.2.27, the callback is being invoked and the key is being generated (using the passphrase specified by the callback, as expected).

May 5 2021, 9:17 PM · gpgme, Bug Report
ikloecker added a comment to T5422: gnupg 2.3.1 breaks gpgme_op_createkey().

The problem might be that gpg tries to ask for a passphrase which fails on the CI. Try setting a passphrase callback and setting the pinentry mode to loopback. See https://dev.gnupg.org/source/gpgme/browse/master/tests/run-genkey.c$435.

May 5 2021, 10:01 AM · gpgme, Bug Report
pnirschl created T5422: gnupg 2.3.1 breaks gpgme_op_createkey().
May 5 2021, 8:33 AM · gpgme, Bug Report

May 4 2021

ikloecker updated the diff for D530: gpgme: Add support for trust signatures to key list result.

Added documentation for the new fields.

May 4 2021, 3:27 PM · gpgme