Page MenuHome GnuPG
Projects gnupg

gnupgProject
ActivePublic
Watch Project

Milestones
View All

Subprojects
View All

Members

  • This project does not have any members.
  • View All

Watchers (2)

Details

Description

Bugs, feature requests, memos, and support related to GnuPG.

Note that the tags gnug24, gnupg26 etc are used to indicate that a certain task is scheduled to be fixed in that version. This tag here is used if there is no concrete version affected or a schedule has not yet been set.

Recent Activity
View All

Thu, Nov 14

• ikloecker changed the status of T7397: Kleopatra: Support Kyber generation, a subtask of T6636: PQC Implementation, from Open to Testing.
Thu, Nov 14, 4:39 PM · PQC, gnupg, libgcrypt

Wed, Nov 6

• ikloecker raised the priority of T7373: gpg --export-secret-keys exits with General error if the password prompt was canceled from Low to Needs Triage.
Wed, Nov 6, 9:03 AM · gnupg

Tue, Nov 5

• ikloecker triaged T7373: gpg --export-secret-keys exits with General error if the password prompt was canceled as Low priority.
Tue, Nov 5, 9:31 PM · gnupg
• ebo closed T5849: "gpg --logger-fd 1" doesn't override log-file in gpg.conf as Resolved.

This looks as if it is resolved. Should I be wrong, you can reopen it.

Tue, Nov 5, 10:18 AM · gnupg, Support

Mon, Nov 4

• ebo changed the status of T7322: Kleopatra: General error if ADSK is not configured correctly from Open to Testing.
Mon, Nov 4, 10:42 AM · Restricted Project, vsd33, gnupg

Sun, Nov 3

• werner added projects to T7368: dirmngr/dns.c files to compile due to type-mismatch caused by missing _XOPEN_SOURCE on Solaris and derivatives: Solaris, gnupg, dns.
Sun, Nov 3, 3:42 PM · dns, gnupg, Solaris, Bug Report

Thu, Oct 31

• ikloecker moved T7322: Kleopatra: General error if ADSK is not configured correctly from Backlog to WiP on the vsd33 board.

Werner backported this to GnuPG 2.2.45.

Thu, Oct 31, 6:49 PM · Restricted Project, vsd33, gnupg
• ebo moved T7322: Kleopatra: General error if ADSK is not configured correctly from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Thu, Oct 31, 3:54 PM · Restricted Project, vsd33, gnupg
• ebo added a project to T7322: Kleopatra: General error if ADSK is not configured correctly: Restricted Project.

ok, regarding better access to the more detailed error dialog see the above mentioned ticket

Thu, Oct 31, 3:54 PM · Restricted Project, vsd33, gnupg

Wed, Oct 30

• ebo added a comment to T7354: Leak of User-ID via clipboard.

Sorry, I've pasted the wrong link, I wanted to paste this one: https://lists.gnupg.org/mailman/listinfo/gnupg-users

Wed, Oct 30, 3:46 PM · kleopatra, gnupg, Bug Report
marcel.proust added a comment to T7354: Leak of User-ID via clipboard.

Why would I turn to the Windows mailing list when I am a Linux user?

Wed, Oct 30, 3:16 PM · kleopatra, gnupg, Bug Report
• ebo closed T7354: Leak of User-ID via clipboard as Invalid.

I removed a duplicated comment above.
Please do not duplicate information (no top posting) and keep your descriptions short and to the point.

Wed, Oct 30, 10:45 AM · kleopatra, gnupg, Bug Report
marcel.proust added a comment to T7354: Leak of User-ID via clipboard.

"BTW, GnuPG 2.3.4 is a very old version."

Wed, Oct 30, 9:43 AM · kleopatra, gnupg, Bug Report
wiktor-k added a comment to T4060: Add ability to mark critical notations as "recognized" during signature verification.

I've checked and can confirm this is working as intended.

Wed, Oct 30, 9:34 AM · gnupg, gpgme, Feature Request
marcel.proust added a comment to T7354: Leak of User-ID via clipboard.
Wed, Oct 30, 9:30 AM · kleopatra, gnupg, Bug Report
marcel.proust added a comment to T7354: Leak of User-ID via clipboard.

In the story of my life, you are a mythological figure.

Wed, Oct 30, 9:28 AM · kleopatra, gnupg, Bug Report
• ikloecker reassigned T7313: gpgconf --list-options does not handle multiple trusted-keys. from • ikloecker to • werner.

Kleopatra just checks if the option "default-new-key-adsk" is set (i.e. it doesn't matter if it's an option with scalar value or list value). The other two options that were changed are not used by Kleopatra.

Wed, Oct 30, 9:11 AM · Feature Request, gnupg
• werner triaged T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key as Normal priority.
Wed, Oct 30, 8:32 AM · gnupg, Bug Report
• werner renamed T7354: Leak of User-ID via clipboard from Major Security Issue: Leak of User-ID via clipboard to Leak of User-ID via clipboard.
Wed, Oct 30, 8:31 AM · kleopatra, gnupg, Bug Report
• werner added a comment to T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.

I reviewed this and there are actually two changes. The first chnage
is a simple string change from

Wed, Oct 30, 8:08 AM · gnupg, Bug Report

Tue, Oct 29

ametzler1 added a comment to T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.

Hello,
I have a hard time to agree that is the right thing for gnupg to throw an error if it successfully imported a revocation certificate for an expired key. This is a meaningful (and not useless) change even if the key is expired.

Tue, Oct 29, 6:13 PM · gnupg, Bug Report
• TobiasFella added a comment to T7335: S/MIME keys are not listed correctly.

Tested again on linux with current master (at 18081e2ecf43de2be6ad5a7ca3384e1e2b66914d) and 2.2 (at 5c0383d558cc9112c4c0984a3b2a6c98b29a92ca) - still same behavior.

Tue, Oct 29, 2:35 PM · gnupg, Bug Report
• werner triaged T7353: Release GnuPG 2.4.7 as Normal priority.
Tue, Oct 29, 2:22 PM · gnupg, Release Info
• werner placed T6500: Keyserver access via http-proxy isn't attempted when using standard-resolver up for grabs.
Tue, Oct 29, 1:32 PM · gnupg, dns, Bug Report
• werner edited projects for T6500: Keyserver access via http-proxy isn't attempted when using standard-resolver, added: gnupg; removed gnupg24.
Tue, Oct 29, 1:32 PM · gnupg, dns, Bug Report
• werner edited projects for T6679: Keyboxd: SQL database disk image is malformed, added: gnupg, Support; removed gnupg24.
Tue, Oct 29, 1:29 PM · Support, gnupg, gpg4win
• ikloecker added a comment to T7322: Kleopatra: General error if ADSK is not configured correctly.
In T7322#192972, @ebo wrote:

Which is of course technically correct but why can't we have the much more clear "invalid ADSK ... specified"? I think this would help troubleshooting.

Tue, Oct 29, 1:26 PM · Restricted Project, vsd33, gnupg
• werner added a comment to T7335: S/MIME keys are not listed correctly.

Was fixed in master with rG374195e741cf1c52daad6c07799d308c8a9f73e3 (bug tag was missing in the commit).

Tue, Oct 29, 1:02 PM · gnupg, Bug Report
• werner moved T4060: Add ability to mark critical notations as "recognized" during signature verification from Backlog to QA for next release on the gpgme board.

Alright, finally supported by gpgme (fot 1.24) For testing you may use

Tue, Oct 29, 12:04 PM · gnupg, gpgme, Feature Request
• ebo edited projects for T7322: Kleopatra: General error if ADSK is not configured correctly, added: vsd33; removed vsd33 (vsd-3.3.0).
Tue, Oct 29, 10:08 AM · Restricted Project, vsd33, gnupg
• ebo added a project to T7322: Kleopatra: General error if ADSK is not configured correctly: vsd33 (vsd-3.3.0).

This is not on any workboard. But I tested it with 4win-Beta-64 and the error shown in Kleopatra is now "Unusable public key".
So I'll put it on vsd33.

Tue, Oct 29, 10:08 AM · Restricted Project, vsd33, gnupg

Mon, Oct 28

• werner added a comment to T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.

Indeed, gpg fixes a long standing bug in that expired trusted-keys were not correctly handled. Thus this error message

Mon, Oct 28, 9:46 AM · gnupg, Bug Report

Sun, Oct 27

ametzler1 created T7351: 2.2.45 exitcode 2 when importing revocation cert for expired key.
Sun, Oct 27, 6:18 PM · gnupg, Bug Report

Fri, Oct 25

• werner edited projects for T4060: Add ability to mark critical notations as "recognized" during signature verification, added: gnupg; removed gnupg (gpg22).

Solved for gnupg 2.2, 2.4 and 2.6. GPGME support still missing.

Fri, Oct 25, 12:10 PM · gnupg, gpgme, Feature Request

Wed, Oct 23

• werner closed T6185: `gpg2 --list-keys --with-colons > /dev/full` exits with status 0 as Resolved.

Also done for gpgsm in gnupg26 (master)

Wed, Oct 23, 11:42 AM · Bug Report, gnupg

Tue, Oct 22

• werner updated the task description for T7255: Release GnuPG 2.2.45.
Tue, Oct 22, 3:31 PM · gnupg22 (gnupg-2.2.45), Release Info

Oct 16 2024

• ikloecker added a project to T7332: Kleopatra: Initial keylisting sometimes fails or hangs for some seconds: gnupg.

The fix should probably be backported to gnupg 2.2 and 2.4.

Oct 16 2024, 4:22 PM · gnupg24, gnupg22, gpd5x, kleopatra, Bug Report

Oct 15 2024

• TobiasFella reopened T7335: S/MIME keys are not listed correctly as "Open".

I'm still seeing the same problems both with current master and 2.2

Oct 15 2024, 11:43 AM · gnupg, Bug Report
• werner closed T7335: S/MIME keys are not listed correctly as Resolved.

FWIW, the cache has not been implemented in 2.4 (which will be used for the next gpg4win) and thus there is no need for a fix there.

Oct 15 2024, 9:46 AM · gnupg, Bug Report
• werner added a comment to T7335: S/MIME keys are not listed correctly.

Was fixed last Thursday with commit rG69a8aefa5bf77136b77383b94e34ba784c1cce89 for 2.2 and will soon make it to master.

Oct 15 2024, 9:43 AM · gnupg, Bug Report

Oct 14 2024

• TobiasFella triaged T7335: S/MIME keys are not listed correctly as High priority.
Oct 14 2024, 12:00 PM · gnupg, Bug Report
• TobiasFella updated the task description for T7335: S/MIME keys are not listed correctly.
Oct 14 2024, 12:00 PM · gnupg, Bug Report
• TobiasFella created T7335: S/MIME keys are not listed correctly.
Oct 14 2024, 11:59 AM · gnupg, Bug Report

Oct 11 2024

• werner closed T6929: Kleopatra: Allow revocation of RSA 2048 keys as Resolved.
Oct 11 2024, 2:25 PM · kleopatra, gnupg

Oct 8 2024

CarlSchwan closed T5364: Kleopatra won't start as Resolved.

gpg4win 4 has been released with unicode support. Closing.

Oct 8 2024, 2:59 PM · workaround, gnupg, Windows, kleopatra, Bug Report, gpg4win
• gniibe changed the status of T7316: Curve25519/v5 key cannot be exported, a subtask of T7315: Allow exporting of PQC keys., from Open to Testing.
Oct 8 2024, 8:38 AM · gnupg26, OpenPGP, PQC, gnupg
• gniibe changed the status of T7316: Curve25519/v5 key cannot be exported from Open to Testing.
Oct 8 2024, 8:38 AM · gnupg26, OpenPGP, PQC, gnupg
• gniibe added a comment to T7316: Curve25519/v5 key cannot be exported.

Pushed the fix for exporting OpenPGP v5 key: rG57dce1ee62c2: common,gpg,scd,sm: Fix for Curve25519 OID supporting new and old.

Oct 8 2024, 8:38 AM · gnupg26, OpenPGP, PQC, gnupg

Oct 7 2024

• ikloecker triaged T7322: Kleopatra: General error if ADSK is not configured correctly as Normal priority.
Oct 7 2024, 5:07 PM · Restricted Project, vsd33, gnupg
• werner added a comment to T7322: Kleopatra: General error if ADSK is not configured correctly.

With the new patch you get this now:

[GNUPG:] KEY_CONSIDERED F40ADB902B24264AA42E50BF92EDB04BFF325CF3 1
[GNUPG:] ERROR add_adsk 53
gpg: key "F40ADB902B24264AA42E50BF92EDB04BFF325CF3!" not found: Unusable public key
gpg: Did you specify the fingerprint of a subkey?
[GNUPG:] FAILURE gpg-exit 33554433
Oct 7 2024, 8:26 AM · Restricted Project, vsd33, gnupg