| Summary: | kgpg shows fingerprint of subkey not of public key | ||
|---|---|---|---|
| Product: | [Applications] kgpg | Reporter: | Wulf <wulf.richartz> |
| Component: | general | Assignee: | Rolf Eike Beer <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 2.17.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kgpg/4b01a60a1f43f2e72b082c815646183593f40ad0 | Version Fixed In: | 16.08.2 |
| Sentry Crash Report: | |||
| Attachments: | screenshot of kgpg with the properties of my key | ||
Tested with 2.17.40, works fine there. Created attachment 100721 [details]
screenshot of kgpg with the properties of my key
screenshot of kgpg with the properties of my key
fingerprint is not for my public key, shown fingerprint is for my sub-key
also verseion 2.17.40
tested with new user Sorry, my fault. My GnuPG shows only one fpr line, so this must work. Will check later on a different machine. I see only one fpr line with both GnuPG 2.0 and 2.1. Which version are you using? My gpg(2) version: $ gpg --help gpg (GnuPG) 2.1.15 libgcrypt 1.7.3 but just compare the fingerprint shown by kgpg with the fingerprint shown by a public keyserver: https://pgp.key-server.io/ I will recheck it with another computer/distro thats weird with pclinux os kgpg works fine :-? kgpg version 2.15.1 gpg(1) --help gpg (GnuPG) 1.4.20 gpg2 --help gpg (GnuPG) 2.0.30 libgcrypt 1.5.4 and you are right both shows only one row with fingerprint this could be the explanation: https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000390.html "* gpg: New option --with-subkey-fingerprint." Git commit 4b01a60a1f43f2e72b082c815646183593f40ad0 by Rolf Eike Beer. Committed on 09/09/2016 at 14:27. Pushed by dakon into branch 'Applications/16.08'. do not set subkey fingerprint as key fingerprint In case GnuPG has the option "with-subkey-fingerprints" configured by default these will show up also in the normal key listing. In this case currentSNode will never be set, which resulted in these fingerprints overwriting the actual key fingerprint. FIXED-IN:16.08.2 M +1 -1 kgpginterface.cpp http://commits.kde.org/kgpg/4b01a60a1f43f2e72b082c815646183593f40ad0 |
kgpg shows fingerprint of subkey not of public key seems top be the same bug as 340782, which es marked as resolved. My Key: gpg --with-colons --with-fingerprint --list-keys E49700C0F9FA6F50 gpg: enabled debug flags: memstat gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 gpg: secmem usage: 0/32768 bytes in 0 blocks tru::1:1471894106:3018869376:3:1:5 pub:u:2048:1:E49700C0F9FA6F50:1265668348:3018869376::u:::scaESCA::::::: fpr:::::::::C038F7601648EA2DD3EDF3ECE49700C0F9FA6F50: uid:u::::1442069376::3B5A3D84C67AE75FDFEB8EDA5D0C115A4AC819E1::Wulf Richartz <wulf.richartz@arcor.de>::::::::: sub:u:2048:1:15FC5D2A3A406629:1265668348:3018869384:::::e:::::: fpr:::::::::F713A36AC6449D7714BAC4B615FC5D2A3A406629: My fingerprint is C038F7601648EA2DD3EDF3ECE49700C0F9FA6F50 but kgpg shows fingerprint of subkey F713A36AC6449D7714BAC4B615FC5D2A3A406629