Page MenuHome GnuPG
Projects gnupg gnupg22

gnupg22Project
ActivePublic
Watch Project

Milestones
View All

Members

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

Watchers (1)

Recent Activity
View All

Fri, Jan 9

• werner moved T7866: Allow separate LDAP keyserver for uploading from QA to WIP on the gnupg26 board.
Fri, Jan 9, 3:50 PM · gnupg22, vsd34, LDAP, Feature Request, gnupg26
timegrid added a comment to T7866: Allow separate LDAP keyserver for uploading.

The behaviour might have changed a bit because of the ldap: prefix i use now, or i have missed this case the last time:
Given some cert on the "download" server, I can find it, if dirmngr.conf contains only the "download" server, or if the "download" server is listed first:

Fri, Jan 9, 2:17 PM · gnupg22, vsd34, LDAP, Feature Request, gnupg26
• werner added a comment to T7866: Allow separate LDAP keyserver for uploading.

Independent of keyserver order in dirmngr.conf, --search-keys still offers keys from the upload server, but the download fails:

Fri, Jan 9, 1:35 PM · gnupg22, vsd34, LDAP, Feature Request, gnupg26
• werner added a comment to T7866: Allow separate LDAP keyserver for uploading.

For "Although the upload server is used for upload, the gpg message still displays the first keyserver" see T8025

Fri, Jan 9, 1:28 PM · gnupg22, vsd34, LDAP, Feature Request, gnupg26
• werner edited projects for T6436: Double pinentry on change password, added: gnupg26; removed gnupg24.
Fri, Jan 9, 11:28 AM · gnupg26, Feature Request, gnupg22, Restricted Project
• werner changed the status of T7840: Oddity with 7816 change_reference_data from Testing to Open.
Fri, Jan 9, 11:27 AM · Bug Report, gnupg22, gnupg26, scd
• werner moved T7840: Oddity with 7816 change_reference_data from QA to Done on the gnupg26 board.
Fri, Jan 9, 11:27 AM · Bug Report, gnupg22, gnupg26, scd
• werner closed T2196: keydb locking can result in deadlock in 2.2 as Resolved.

That was fixed with 2.2.52 which fixed a bug in the fix done in 2.2.50 (see rG31fef13df1). Note that 2.2.48 to 2.2.50 had only internal releases.

Fri, Jan 9, 11:15 AM · gnupg22 (gnupg-2.2.52), Bug Report

Thu, Jan 8

• werner raised the priority of T6644: GnuPG: Allow non compliant signatures in compliance mode from Wishlist to Normal.
Thu, Jan 8, 1:21 PM · vsd, gpd5x, kleopatra, gnupg22

Mon, Jan 5

timegrid moved T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server from QA to Done on the gnupg26 board.
Mon, Jan 5, 12:54 PM · gnupg22 (gnupg-2.2.52), gnupg26, Feature Request, gpd5x
timegrid moved T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server from WIP to Done on the gpd5x board.

The problem was the keyserver configuration, which does not include a scheme (ldap:):

keyserver ldap.gnupg.test:389:uid=LordPrivySeal,ou=GnuPG Users,dc=gnupg,dc=test:pass:dc=gnupg,dc=test:
Mon, Jan 5, 12:53 PM · gnupg22 (gnupg-2.2.52), gnupg26, Feature Request, gpd5x

Thu, Dec 18

• werner placed T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server up for grabs.
Thu, Dec 18, 12:11 PM · gnupg22 (gnupg-2.2.52), gnupg26, Feature Request, gpd5x
• werner moved T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server from WIP to QA on the gnupg26 board.
Thu, Dec 18, 12:11 PM · gnupg22 (gnupg-2.2.52), gnupg26, Feature Request, gpd5x
• werner added a comment to T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server.

Well, I tested this again. I created a new key and saved a copy. The I updated the expiration date to 2035 and sent the key to the LDAP server. Then I deleted the updated key locally and imported the old copy. Thus I have now:

Thu, Dec 18, 12:09 PM · gnupg22 (gnupg-2.2.52), gnupg26, Feature Request, gpd5x

Dec 12 2025

timegrid updated the task description for T6719: Support Proxy-Authorization: Negotiate on Windows.
Dec 12 2025, 3:09 PM · Active Directory, test on hold, gpd5x, gnupg24, gnupg22, Feature Request
timegrid added a project to T6719: Support Proxy-Authorization: Negotiate on Windows: test on hold.
Dec 12 2025, 3:07 PM · Active Directory, test on hold, gpd5x, gnupg24, gnupg22, Feature Request
timegrid moved T6719: Support Proxy-Authorization: Negotiate on Windows from WiP to QA on the gnupg22 board.
Dec 12 2025, 3:07 PM · Active Directory, test on hold, gpd5x, gnupg24, gnupg22, Feature Request
timegrid moved T6719: Support Proxy-Authorization: Negotiate on Windows from QA to done on the gnupg24 board.
Dec 12 2025, 3:06 PM · Active Directory, test on hold, gpd5x, gnupg24, gnupg22, Feature Request
timegrid moved T6719: Support Proxy-Authorization: Negotiate on Windows from WiP to QA on the gnupg24 board.
Dec 12 2025, 3:06 PM · Active Directory, test on hold, gpd5x, gnupg24, gnupg22, Feature Request
timegrid moved T6719: Support Proxy-Authorization: Negotiate on Windows from Backlog to QA on the gpd5x board.
Dec 12 2025, 3:05 PM · Active Directory, test on hold, gpd5x, gnupg24, gnupg22, Feature Request
timegrid edited projects for T6719: Support Proxy-Authorization: Negotiate on Windows, added: gpd5x; removed Restricted Project.
Dec 12 2025, 3:05 PM · Active Directory, test on hold, gpd5x, gnupg24, gnupg22, Feature Request
• ebo removed a project from T1235: adding automatic refresh-key: Restricted Project.
Dec 12 2025, 2:27 PM · gnupg26, gnupg22, Feature Request
• ebo moved T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server from QA to WIP on the gnupg26 board.
Dec 12 2025, 1:30 PM · gnupg22 (gnupg-2.2.52), gnupg26, Feature Request, gpd5x
• ebo closed T7332: Kleopatra: Initial keylisting sometimes fails or hangs for some seconds as Resolved.

we haven't seen this in a while…

Dec 12 2025, 10:49 AM · gnupg22 (gnupg-2.2.52), gnupg24, gpd5x, kleopatra, Bug Report

Dec 5 2025

• ebo added a project to T7251: Autofetch signature keys used by a trusted introducer: gpd5x.
Dec 5 2025, 9:42 AM · gpd5x, vsd34, Feature Request, gnupg22
• ebo edited projects for T7251: Autofetch signature keys used by a trusted introducer, added: vsd34; removed Restricted Project.
Dec 5 2025, 9:41 AM · gpd5x, vsd34, Feature Request, gnupg22

Dec 4 2025

timegrid closed T7855: keybox/keydb locking issue in 2.6 , a subtask of T2196: keydb locking can result in deadlock in 2.2, as Resolved.
Dec 4 2025, 3:01 PM · gnupg22 (gnupg-2.2.52), Bug Report

Nov 28 2025

timegrid changed the status of T7730: gpg: retrieve a certificate from an LDAP server before sending it to the LDAP server from Testing to Open.

This seems not to work in Kleopatra/gpg in gpg4win-5.0.0-beta413 @ win11.

Nov 28 2025, 9:59 AM · gnupg22 (gnupg-2.2.52), gnupg26, Feature Request, gpd5x

Nov 27 2025

timegrid changed the status of T7866: Allow separate LDAP keyserver for uploading from Testing to Open.

Tested on gpg4win-5.0.0-beta413 @ win11 with the following entries in dirmngr.conf:

Nov 27 2025, 2:04 PM · gnupg22, vsd34, LDAP, Feature Request, gnupg26

Nov 21 2025

• alexk added a project to T7866: Allow separate LDAP keyserver for uploading: gnupg22.
Nov 21 2025, 4:09 PM · gnupg22, vsd34, LDAP, Feature Request, gnupg26

Nov 19 2025

• werner moved T7914: Card s/n number missing in gpgsm from WIP to QA on the gnupg26 board.
Nov 19 2025, 5:42 PM · gnupg22 (gnupg-2.2.52), scd, S/MIME, Feature Request, gnupg26

Nov 18 2025

• werner added a project to T7133: Add feature to load designated revoker from LDAP: backport.
Nov 18 2025, 8:01 PM · backport, vsd34, Feature Request, gnupg22

Nov 16 2025

• werner moved T7914: Card s/n number missing in gpgsm from Backlog to WiP on the gnupg22 board.
Nov 16 2025, 7:12 PM · gnupg22 (gnupg-2.2.52), scd, S/MIME, Feature Request, gnupg26
• werner edited projects for T7914: Card s/n number missing in gpgsm, added: gnupg22; removed gnupg.
Nov 16 2025, 7:12 PM · gnupg22 (gnupg-2.2.52), scd, S/MIME, Feature Request, gnupg26

Nov 14 2025

• werner edited projects for T7133: Add feature to load designated revoker from LDAP, added: vsd34; removed vsd33.
Nov 14 2025, 12:45 PM · backport, vsd34, Feature Request, gnupg22

Nov 13 2025

• ebo edited projects for T6644: GnuPG: Allow non compliant signatures in compliance mode, added: gpd5x, vsd; removed Restricted Project.

meanwhile it looks like this in Kleopatra, it has now the blue sign but the issue is still the same:

Nov 13 2025, 10:50 AM · vsd, gpd5x, kleopatra, gnupg22

Nov 5 2025

• ebo edited projects for T7333: Allow gpg to auto-upload a new own key to LDAP servers, added: vsd34; removed vsd33.
Nov 5 2025, 11:56 AM · vsd34, gnupg26, gnupg22

Nov 3 2025

• werner raised the priority of T7251: Autofetch signature keys used by a trusted introducer from Normal to High.
Nov 3 2025, 2:05 PM · gpd5x, vsd34, Feature Request, gnupg22

Oct 23 2025

timegrid moved T7829: w32: daemon (gpg-agent/keyboxd/dirmngr) startup and connection race when there is a socket file already from QA to Done on the gpd5x board.

Looks good to me on gpg4win-5.0.0-beta395 @ win11 (gpg 2.5.13).

Oct 23 2025, 2:45 PM · gnupg22 (gnupg-2.2.52), Bug Report, gpd5x, okular

Oct 22 2025

• ebo moved T7829: w32: daemon (gpg-agent/keyboxd/dirmngr) startup and connection race when there is a socket file already from WIP to QA on the gpd5x board.
Oct 22 2025, 4:32 PM · gnupg22 (gnupg-2.2.52), Bug Report, gpd5x, okular
• werner changed the status of T7840: Oddity with 7816 change_reference_data from Open to Testing.
Oct 22 2025, 2:23 PM · Bug Report, gnupg22, gnupg26, scd
• gniibe changed the status of T7855: keybox/keydb locking issue in 2.6 , a subtask of T2196: keydb locking can result in deadlock in 2.2, from Open to Testing.
Oct 22 2025, 4:38 AM · gnupg22 (gnupg-2.2.52), Bug Report

Oct 21 2025

• gniibe changed the status of T7829: w32: daemon (gpg-agent/keyboxd/dirmngr) startup and connection race when there is a socket file already from Open to Testing.

Fixed in master: rGae431b04370f: w32:common: Take care of possible race on startup under Windows.

Oct 21 2025, 9:18 AM · gnupg22 (gnupg-2.2.52), Bug Report, gpd5x, okular

Oct 13 2025

• werner moved T7829: w32: daemon (gpg-agent/keyboxd/dirmngr) startup and connection race when there is a socket file already from Backlog to QA on the gnupg22 board.
Oct 13 2025, 4:00 PM · gnupg22 (gnupg-2.2.52), Bug Report, gpd5x, okular
• werner added a project to T7829: w32: daemon (gpg-agent/keyboxd/dirmngr) startup and connection race when there is a socket file already: gnupg22.
Oct 13 2025, 4:00 PM · gnupg22 (gnupg-2.2.52), Bug Report, gpd5x, okular
• werner changed the status of T2196: keydb locking can result in deadlock in 2.2 from Open to Testing.
Oct 13 2025, 3:45 PM · gnupg22 (gnupg-2.2.52), Bug Report

Oct 9 2025

• werner renamed T2196: keydb locking can result in deadlock in 2.2 from keydb locking can result in deadlock to keydb locking can result in deadlock in 2.2.
Oct 9 2025, 5:54 PM · gnupg22 (gnupg-2.2.52), Bug Report
• werner added a subtask for T2196: keydb locking can result in deadlock in 2.2: T7855: keybox/keydb locking issue in 2.6 .
Oct 9 2025, 2:34 PM · gnupg22 (gnupg-2.2.52), Bug Report

Oct 7 2025

• werner updated the task description for T2196: keydb locking can result in deadlock in 2.2.
Oct 7 2025, 4:11 PM · gnupg22 (gnupg-2.2.52), Bug Report
• werner raised the priority of T2196: keydb locking can result in deadlock in 2.2 from Low to High.

We recently noticed problem at a customer site with creating the standard rsa3072 keys. It basically stopped working. A likely cause for this seems to be some anti-malware software slowing down file system calls. In the wake of this we looked again at our file locking strategy and found a few things which are not as they should be. For example the release of the lock before a Close call. Trying to fix this unfortunately caused other problems, thus a couple of fixes are needed.

Oct 7 2025, 4:09 PM · gnupg22 (gnupg-2.2.52), Bug Report