The advantage of using a fingerprint for referencing a key is that there won't be any collisions in the keyid. Further this unifies the schema with an LDS (Windows) installation where DNs must anyway be unique. But take care the client needs to support this new flag. This will be the case for gnupg >= 2.5.12 (cf. T7756)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Tue, Sep 2
Tue, Sep 2
• werner moved T7742: Extend the LDAP scheme for non-NTDS installations from WIP to QA on the gnupg26 board.
Aug 14 2025
Aug 14 2025
• alexk triaged T7779: dirmngr: use different keyserver for sending and receiving certificates as Normal priority.
Aug 4 2025
Aug 4 2025
• werner changed the status of T7742: Extend the LDAP scheme for non-NTDS installations from Open to Testing.
Jul 25 2025
Jul 25 2025
May 8 2025
May 8 2025
• werner moved T4021: dirmngr: dirmngr/dns.c issue with 127.0.0.1 from WiP to QA on the gnupg24 board.
Apr 7 2025
Apr 7 2025
• ebo moved T4021: dirmngr: dirmngr/dns.c issue with 127.0.0.1 from Backlog to WiP on the gnupg24 board.
• werner edited projects for T4021: dirmngr: dirmngr/dns.c issue with 127.0.0.1, added: gnupg24; removed gnupg.
• gniibe changed the status of T4021: dirmngr: dirmngr/dns.c issue with 127.0.0.1 from Open to Testing.
Fix pushed by: rG1ed8b0e7b403: dirmngr: Fix libdns with 127.0.0.1.
For Linux kernel, once, it was proposed:
https://patchwork.ozlabs.org/project/netdev/patch/1490748756.24891.27.camel@edumazet-glaptop3.roam.corp.google.com/
Another problem with same cause (possibly) is reported: https://lists.gnupg.org/pipermail/gnupg-devel/2025-April/035845.html